From owner-freebsd-bugs@FreeBSD.ORG  Sat Oct 29 02:39:36 2011
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@hub.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 7FFA7106564A;
	Sat, 29 Oct 2011 02:39:36 +0000 (UTC)
	(envelope-from dougb@FreeBSD.org)
Received: from freefall.freebsd.org (freefall.freebsd.org
	[IPv6:2001:4f8:fff6::28])
	by mx1.freebsd.org (Postfix) with ESMTP id 58DA68FC08;
	Sat, 29 Oct 2011 02:39:36 +0000 (UTC)
Received: from freefall.freebsd.org (localhost [127.0.0.1])
	by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p9T2daOm096015;
	Sat, 29 Oct 2011 02:39:36 GMT
	(envelope-from dougb@freefall.freebsd.org)
Received: (from dougb@localhost)
	by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p9T2daBF096011;
	Sat, 29 Oct 2011 02:39:36 GMT (envelope-from dougb)
Date: Sat, 29 Oct 2011 02:39:36 GMT
Message-Id: <201110290239.p9T2daBF096011@freefall.freebsd.org>
To: ler@lerctr.org, dougb@FreeBSD.org, freebsd-bugs@FreeBSD.org,
	dougb@FreeBSD.org
From: dougb@FreeBSD.org
Cc: 
Subject: Re: bin/162135: remote syslog not logging
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 29 Oct 2011 02:39:36 -0000

Synopsis: remote syslog not logging

State-Changed-From-To: open->closed
State-Changed-By: dougb
State-Changed-When: Sat Oct 29 02:36:36 UTC 2011
State-Changed-Why: 

This is something that needs to be reported on a mailing list first, probably
freebsd-questions@FreeBSD.org. If you don't get a resolution there, then try
freebsd-current@FreeBSD.org. 

Meanwhile, make sure that syslogd on the receiving host has not been started
with any -s options.

hope this helps,

Doug


Responsible-Changed-From-To: freebsd-bugs->dougb
Responsible-Changed-By: dougb
Responsible-Changed-When: Sat Oct 29 02:36:36 UTC 2011
Responsible-Changed-Why: 

I closed it.

http://www.freebsd.org/cgi/query-pr.cgi?pr=162135