Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - agoree407

#1
Quote from: axsdenied on June 01, 2023, 05:57:25 PM
I'm not sure I understand the use case.  i.e. Why are we storing the config on a usb stick?  It can't be for backup as that can still get corrupted?

I spin up virtual appliances built from a master image that needs a simple config update for networking config before ansible et al. takes over.  This is mainly a relic from pfSense ("upgrading" to OPNsense bc it has the features I need :) ) which would auto load from a USB stick if it found one plugged in (I simulate this w/Libvirt commands).

I did get it working by placing the script in /usr/local/etc/rc.syshook.d/start/ (instead of 'early') amongst changes I made to my rc script.  8)

#2
It looks like officially, my location should work, according to https://docs.opnsense.org/development/backend/autorun.html

"Syshook scripts should be installed in:

/usr/local/etc/rc.syshook.d/<subdir>/"

My script is located at "/usr/local/etc/rc.syshook.d/early/17-opnsensectl" :o
#3
I have a custom rc script that I use to load a config.xml from a USB if it finds it plugged in (similar to the functionality that was removed or never added from pfSense code, see https://forum.opnsense.org/index.php?topic=3297.0).

This worked fine before but after an upgrade to 23.1.8, my systems now fail to boot and are punted to single-user mode (error in attached image).

Is there a recommended/expected place for startup scripts to be located in order to avoid the given error?  I currently have my script located at /usr/local/etc/rc.syshook.d/early/17-opnsensectl