Date: Mon, 12 Jan 2004 14:53:32 +0100 From: Bernd Walter <ticso@cicely12.cicely.de> To: David Malone <dwmalone@maths.tcd.ie> Cc: freebsd-current@freebsd.org Subject: Re: Problems with syslogd under 5.2-RELEASE Message-ID: <20040112135332.GT51502@cicely12.cicely.de> In-Reply-To: <20040112113643.GA54144@walton.maths.tcd.ie> References: <20040112113040.GC19402@genius.tao.org.uk> <20040112113643.GA54144@walton.maths.tcd.ie>
next in thread | previous in thread | raw e-mail | index | archive | help
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. I always see this on systems at boot with lots off dmesg info and slow logging disk. -- B.Walter BWCT http://www.bwct.de ticso@bwct.de info@bwct.de
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040112135332.GT51502>