Startup scripts are located in
/.readonly/etc/init.d
The logger is
/.readonly/etc/init.d/rsyslog
We reduced the number of startup scripts to reduce bootup
time. However, there is no reason you cannot start them yourself whenever you want, or modify the bootup startup scripts.
To start it yourself do
/etc/init.d/rsyslog start
To stop it yourself do
/etc/init.d/rsyslog stop
To have it automatically start on boot make a symbolic link in the /.readonly/etc/rc2.d folder to rsyslog
For example:
mount -o remount,rw /
cd /.readonly/etc/rc2.d
ln -s ../init.d/rsyslog S11rsyslog
mount -o remount,ro /
The way debian linux startup scripts works is if there is a filename in the /etc/rc2.d folder starting with S it automatically calls that script with the start parameter after it. If there is a K at the beginning of the filename it automatically calls the script with the stop parameter. The startup order is determined by the number after the S.
The numbers need not be in sequence but the startup sequence relative to other S## is determined by the value of the number.
This rule applies to the folders /etc/rcS , /etc/rc0.d, rc1.d .. rc6.d. Go to http://en.wikipedia.org/wiki/Runlevel for some basics if you want to know about administering your system.
The above worked GREAT for me (THANKS), except I noticed that after rebooting the Power PMAC, the /var/log/messages file gets clobbered. I also saw that no backup files (/var/log/messages.1, /var/log/messages.2, etc) got created. So, the benefits of using syslog (log rollover/cleanup of old logs) is lost? Or am I missing something? Should I be looking for my logged messages elsewhere?