I want to keep the changes to /etc/rc.server as minimal as possible. So I will add two lines at the very end of the file that will do two things in a conditional:
# org.bogs.maintenance
if [ -e /private/tmp/org.bogs.maintenance-mode ] ; then source /var/root/Scripts/maintenance.sh ; fi
The file /tmp/org.bogs.maintenance-mode is used to pass parameters to ~root/Scripts/maintenance.sh. If it is not present, then this is not a maintenance boot. If it is present, but if the maintenance.sh script is missing, an error message "no such file or directory" will be written to the log. Note that maintenance.sh runs in the same bash environment as rc.server. Also note that ~root is already a protected place, and Scripts should also be protected (mode 700).
Also note that /tmp will be erased at some point after the maintenance has completed and the system comes up multiuser.
The file maintenance.sh should not do very much, its role is to call other scripts or programs located in the same directory based on the contents of org.bogs.maintenance-mode.
All of the maintenance code will be maintained elsewhere, on another system, and be copied into a directory on the server and installed from there into /var/root and /etc/rc.server. In addition, the installation script will add or replace the last two lines of rc.server, and will also add the appropriate material to /Library/LaunchDaemons (which is where "system-wide daemons provided by the administrator" are supposed to go).
1 comment:
Just a quick note to say that on my non-server powerbook, I created a file called /etc/rc.server and just put in some lines to get a message written into /var/log/system.log as a test, and it worked just like on the server. Therefore, it seems as if rc.server is a general-purpose boot-time hook that can be used for maintenance-related purposes. Therefore, the backup et al. scripts I am working on for the server might also be usable on non-server macs.
Post a Comment