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. 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. > Nope. This hoses my system completely. These boot messages print: Sure! RTFM > syslog: /dev/xconsole: Interrupted system call > syslogd: unknown priority name "..]" > syslogd: unknown priority name "" > > and then hangs. Please check your /etc/syslog.conf file. This mistake sounds very strange to me. Joey -- / Martin Schulze * Debian GNU/Linux Developer * [EMAIL PROTECTED] / / http://www.debian.org/ http://home.pages.de/~joey/
