[5527] in RedHat Linux List
Again: Why is syslogd blocking telinit ?
daemon@ATHENA.MIT.EDU (Kyle Ferrio)
Thu Nov 21 21:45:47 1996
Date: Thu, 21 Nov 1996 21:41:16 -0500 (EST)
From: Kyle Ferrio <kbf@phy.duke.edu>
To: redhat-list@redhat.com
In-Reply-To: <19961122032204.23344.qmail@brouhaha.com>
Resent-From: redhat-list@redhat.com
Reply-To: redhat-list@redhat.com
I didn't get an answer to this.
I know that if my question was *really* stupid, I'd have a stuffed
mailbox. So I'm asking again in the hope that this is only semi-stupid. :)
The system is Colgate with all the latest updates.
The problem is that both 'telinit s' and 'telinit -t 0 s' fail to change
the runlevel. In fact, in the former example, the KILL never gets sent
after the (default) 5-second timeout for TERM. AT this point the system
is quasi-hung; runlevel 3 can be achieved with a CTRL-C.
Trial and error reveals that this behavior occurs when syslogd is loaded,
as it generally would be before taking the system down to single-user mode.
A successful 'telinit s' requires that syslogd be killed first.
Is this a bug? If not, why not? If so, what's up?
TIA,
Kyle Ferrio
--
PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
________________________________________________________________________
http://www.redhat.com/RedHat-FAQ http://www.redhat.com/RedHat-Errata
http://www.redhat.com/RedHat-Tips http://www.redhat.com/mailing-lists
------------------------------------------------------------------------
To unsubscribe: mail -s unsubscribe redhat-list-request@redhat.com < /dev/null
