From owner-freebsd-current@FreeBSD.ORG  Mon Jan 12 03:36:46 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 09E0D16A4CE; Mon, 12 Jan 2004 03:36:46 -0800 (PST)
Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11])
	by mx1.FreeBSD.org (Postfix) with SMTP
	id 74FC743D2F; Mon, 12 Jan 2004 03:36:44 -0800 (PST)
	(envelope-from dwmalone@maths.tcd.ie)
Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP
          id <aa53073@salmon>; 12 Jan 2004 11:36:43 +0000 (GMT)
Date: Mon, 12 Jan 2004 11:36:43 +0000
From: David Malone <dwmalone@maths.tcd.ie>
To: Josef Karthauser <joe@FreeBSD.org>
Message-ID: <20040112113643.GA54144@walton.maths.tcd.ie>
References: <20040112113040.GC19402@genius.tao.org.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20040112113040.GC19402@genius.tao.org.uk>
User-Agent: Mutt/1.5.3i
Sender: dwmalone@maths.tcd.ie
cc: freebsd-current@FreeBSD.org
Subject: Re: Problems with syslogd under 5.2-RELEASE
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Jan 2004 11:36:46 -0000

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.

	David.