From owner-freebsd-questions@FreeBSD.ORG  Tue Nov 29 08:25:41 2011
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 1F3741065670
	for <freebsd-questions@freebsd.org>;
	Tue, 29 Nov 2011 08:25:41 +0000 (UTC)
	(envelope-from bonomi@mail.r-bonomi.com)
Received: from mail.r-bonomi.com (mx-out.r-bonomi.com [204.87.227.120])
	by mx1.freebsd.org (Postfix) with ESMTP id CA8CC8FC0C
	for <freebsd-questions@freebsd.org>;
	Tue, 29 Nov 2011 08:25:40 +0000 (UTC)
Received: (from bonomi@localhost)
	by mail.r-bonomi.com (8.14.4/rdb1) id pAT8RAoo076004
	for freebsd-questions@freebsd.org; Tue, 29 Nov 2011 02:27:10 -0600 (CST)
Date: Tue, 29 Nov 2011 02:27:10 -0600 (CST)
From: Robert Bonomi <bonomi@mail.r-bonomi.com>
Message-Id: <201111290827.pAT8RAoo076004@mail.r-bonomi.com>
To: freebsd-questions@freebsd.org
In-Reply-To: <4ED440EF.8000604@a1poweruser.com>
Subject: Re: Alternative to syslogd that actually writes external logs to
	files?
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Nov 2011 08:25:41 -0000

Fbsd8 <fbsd8@a1poweruser.com> wrote;
>
> You have never said if you restarted syslog after making your changes to 
> syslog.conf, you have to reboot your box or restart syslog for the 
> changes to take effect.

Need I point out that the FM says that 'kill -HUP' of syslogd will cause
it to reread it's configuration file -- just as id it was stopped and
restarted ?    <grin>