Mike Tancsa wrote:
>
> Yeah, I had a similar problem to this in the past where syslogd was kind of
> hung, and the su was blocking waiting for I guess syslog to return. If you
> can login as root on the console, kill syslogd, restart it and see if su
> works once again.
Nope, it does not work again. But after a couple of seconds after
restarting syslogd I've got this messages on the console:
"syslogd: timed out waiting for child"
Another note, syslogd does not go with a normal kill, it needs a kill -9
to make it into heaven.
Could this be related to having a serial console?
--
Andre
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
