Martin Schulze wrote: > > Ken Gaugler writes: > > > > > For some reason syslogd refuses to start in the /etc/init.d/sysklogd > > > > file. The docs say to use a -n command line argument if starting > > > > syslogd from the inits, but at bootup I see the message > > > > "-n unknown option" and it still doesn't start. > > > > > > because, written as it is shown below, you're passing -n to > > > start-stop-daemon, > > > not to syslogd (I discovered this with another daemon, but think it is > > > valid to > > > syslogd too) > > > > > > > I can start it manually just fine, but that is a pain. I did nothing > > > > special to this system, so I assume others must have had this happen, > > > > too. > > > > start-stop-daemon --start --quiet --exec /sbin/syslogd -n -- > > > > $SYSLOGD > > This actually means that -n is an argument to start-stop-daemon > > > > start-stop-daemon --start --quiet --exec /sbin/syslogd -- -n $SYSLOGD > > Now it's an argument for /sbin/syslogd. >
This still hoses my system. > but please read the manual again to find yout what -n does. > > IT TURNS OFF AUTO-BACKGROUNDING. This means that YOUR SYSTEM WILL > WAIT UNTIL SYSLOGD DIES - which won't be the case for sure. > According to the manpages, -n Avoid auto-backgrounding. This is needed especially if the syslogd is started and controlled by init(8). My system, originally a 1.1 system, has syslog starting from the /etc/init.d/sysklogd file. This is init, as far as I know. > > Nope. This hoses my system completely. These boot messages print: > > Sure! RTFM > Thanks, but so far the docs have not been very illuminating. -- Ken Gaugler N6OSK Santa Clara, California email: [EMAIL PROTECTED] URL: http://www.wco.com/~keng "The life of a Repo Man is always INTENSE..."