Problems with syslogd under 5.2-RELEASE
joe at FreeBSD.org
Mon Jan 12 04:46:01 PST 2004
On Mon, Jan 12, 2004 at 11:36:43AM +0000, David Malone wrote:
> On Mon, Jan 12, 2004 at 11:30:40AM +0000, Josef Karthauser wrote:
> > If I kill and restart syslogd by hand I get:
> > # /usr/sbin/syslogd -s
> > syslogd: timed out waiting for child
> > Is this a known problem? Is there a workaround?
> Is your console in some wird state? (XOFF, scroll-lock-on, ...)
> There have been reports of problems like this before, but they've
> been hard to pin point.
Maybe, I'm running a serial console on this machine, and I changed over
to it at the same time as the problems began (at the same time I
upgraded to 5.2). The serial console is a remote serial port connected
to a Cisco box.
Josef Karthauser (joe at tao.org.uk) http://www.josef-k.net/
FreeBSD (cvs meister, admin and hacker) http://www.uk.FreeBSD.org/
Physics Particle Theory (student) http://www.pact.cpes.sussex.ac.uk/
================ An eclectic mix of fact and theory. =================
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 195 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20040112/bd278bbb/attachment.bin
More information about the freebsd-current