Re: syslogd will not start
On 15:25:22 Hamish Moffatt wrote: >>On Sat, Apr 05, 1997 at 11:04:39AM -0700, Rick Macdonald wrote: >> Speaking of syslogd, when I boot the machine it hangs for 5 ro 10 seconds >> when syslogd starts. It didn't used to. >> I'm running from unstable. Anybody know what it's doing? > >Does this here too ... Keeps the machine at high CPU load for that >time too. (*) > I see this here on 1.1 also, but I thought it might be due to my system losing the sense of "who" it is! I no longer see the hostname on the login prompt, or if I do a uname -a , for example. And, no info goes to /var/log/messages (since syslogd doesn't start I presume). Where else, other than the /etc/hostname does it keep what it believes to be the hostname of the system? If I knew that, I think I could fix this on my endI think!? Paul
Re: syslogd will not start
Elie Rosenblum writes: > On Sat, 5 Apr 1997, Ken Gaugler wrote: > > 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. > > When it says 'starting from init', it means 'starting from /etc/inittab.' Correct, you got it. Joey -- / Martin Schulze * Debian GNU/Linux Developer * [EMAIL PROTECTED] / / http://www.debian.org/ http://home.pages.de/~joey/
Re: syslogd will not start
Moin Ken! > > 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. Sure! If a program is executed at boot time which doesn't put itself in the background the system will wait for its termination. > > 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. No! This is not init, it is init.d. If you want it controlled by init, then you have to put a line similar to the next in /etc/inittab: sy:123456:respawn:/sbin/syslogd -n Joey -- / Martin Schulze * Debian GNU/Linux Developer * [EMAIL PROTECTED] / / http://www.debian.org/ http://home.pages.de/~joey/
Re: syslogd will not start
On Sat, Apr 05, 1997 at 11:04:39AM -0700, Rick Macdonald wrote: > Speaking of syslogd, when I boot the machine it hangs for 5 ro 10 seconds > when syslogd starts. It didn't used to. > I'm running from unstable. Anybody know what it's doing? Does this here too ... Keeps the machine at high CPU load for that time too. (*) Hamish (* I can tell from the fan speed on my Cyrix. :-) -- Hamish Moffatt, StudIEAust[EMAIL PROTECTED] Student, computer science & computer systems engineering.3rd year, RMIT. http://yallara.cs.rmit.edu.au/~moffatt (PGP key here) CPOM: [ ] 40%
Re: syslogd will not start
On Sat, 5 Apr 1997, Ken Gaugler wrote: > 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. When it says 'starting from init', it means 'starting from /etc/inittab.' --- Elie Rosenblum <[EMAIL PROTECTED]> That is not dead which can eternal lie, <[EMAIL PROTECTED]> And with strange aeons even death may die. Mail System Administrator, Erol's Internet- _The Necromicon_
Re: syslogd will not start
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..."
Re: syslogd will not start
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/
Re: syslogd will not start
On Apr 5, Rick Macdonald wrote > On Sat, 5 Apr 1997, Rick Macdonald wrote: > > > Here's mine. I didn't change mine either! > > > > > > case "$1" in > > start) > > echo -n "Starting system log daemon: syslogd" > > start-stop-daemon --start --quiet --exec /sbin/syslogd -- $SYSLOGD > > Speaking of syslogd, when I boot the machine it hangs for 5 ro 10 seconds > when syslogd starts. It didn't used to. > > I'm running from unstable. Anybody know what it's doing? It's just sleeping ;-) Seems to be a quick and dirty hack which came from the upstream source to solve problems with bash2.0. Hopefully it will be solved more cleanly in the near future. Greetings, Christian -- Christian Meder, email: [EMAIL PROTECTED] What's the railroad to me ? I never go to see Where it ends. It fills a few hollows, And makes banks for the swallows, It sets the sand a-blowing, And the blackberries a-growing. (Henry David Thoreau)
Re: syslogd will not start
[EMAIL PROTECTED] wrote: > > > > > 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 > > try this > > start-stop-daemon --start --quiet --exec /sbin/syslogd -- -n $SYSLOGD > > HTH > > -- > |||| ||| Marco Frattola Microsoft is not the > answer > ||`..'|| |||... Piacenza, ItalyMicrosoft is the question > ||| ||| |||''[EMAIL PROTECTED]"No" is the answer > ||| ||| ||| www.enjoy.it/users/~mk/index.html Live Linux, live free! Nope. This hoses my system completely. These boot messages print: syslog: /dev/xconsole: Interrupted system call syslogd: unknown priority name "..]" syslogd: unknown priority name "" and then hangs. Thanks anyway! -- Ken Gaugler N6OSK Santa Clara, California email: [EMAIL PROTECTED] URL: http://www.wco.com/~keng "The life of a Repo Man is always INTENSE..."
Re: syslogd will not start
On Sat, 5 Apr 1997, Rick Macdonald wrote: > Here's mine. I didn't change mine either! > > > case "$1" in > start) > echo -n "Starting system log daemon: syslogd" > start-stop-daemon --start --quiet --exec /sbin/syslogd -- $SYSLOGD Speaking of syslogd, when I boot the machine it hangs for 5 ro 10 seconds when syslogd starts. It didn't used to. I'm running from unstable. Anybody know what it's doing? ...RickM...
Re: syslogd will not start
On Sat, 5 Apr 1997, Ken Gaugler wrote: > 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. > Here are the lines in my /etc/init.d/sysklogd file: > > SYSLOGD="" > > # Use KLOGD="-k /boot/System.map-2.0" to specify System.map > # > KLOGD="" > > case "$1" in > start) > echo -n "Starting system log daemon: syslogd" > start-stop-daemon --start --quiet --exec /sbin/syslogd -n -- > $SYSLOGD Here's mine. I didn't ch9ange mine either! case "$1" in start) echo -n "Starting system log daemon: syslogd" start-stop-daemon --start --quiet --exec /sbin/syslogd -- $SYSLOGD ...RickM...
syslogd will not start
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. 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. What is the secret? Here are the lines in my /etc/init.d/sysklogd file: SYSLOGD="" # Use KLOGD="-k /boot/System.map-2.0" to specify System.map # KLOGD="" case "$1" in start) echo -n "Starting system log daemon: syslogd" start-stop-daemon --start --quiet --exec /sbin/syslogd -n -- $SYSLOGD -- Ken Gaugler N6OSK Santa Clara, California email: [EMAIL PROTECTED] URL: http://www.wco.com/~keng "The life of a Repo Man is always INTENSE..."