From owner-freebsd-stable@FreeBSD.ORG  Mon Nov 20 22:40:52 2006
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
X-Original-To: freebsd-stable@freebsd.org
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id 8091E16A415
	for <freebsd-stable@freebsd.org>; Mon, 20 Nov 2006 22:40:52 +0000 (UTC)
	(envelope-from bri@sonicboom.org)
Received: from entwistle.sonicboom.org (entwistle.sonicboom.org [66.93.34.170])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 6311343D7F
	for <freebsd-stable@freebsd.org>; Mon, 20 Nov 2006 22:40:26 +0000 (GMT)
	(envelope-from bri@sonicboom.org)
Received: from [127.0.0.1] (entwistle.sonicboom.org [66.93.34.170])
	by entwistle.sonicboom.org (8.13.8/8.13.8) with ESMTP id kAKMeiZn092880
	for <freebsd-stable@freebsd.org>; Mon, 20 Nov 2006 14:40:44 -0800 (PST)
	(envelope-from bri@sonicboom.org)
Message-ID: <45622EEC.6030907@sonicboom.org>
Date: Mon, 20 Nov 2006 14:40:44 -0800
From: Brian <bri@sonicboom.org>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To: freebsd-stable@freebsd.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: 6.2 rc file problems
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, 
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Nov 2006 22:40:52 -0000

I've started getting emails like this for the last few days after a 
system build.

newsyslog: can't open pid file: /var/run/syslog.pid: No such file or directory
newsyslog: log /var/log/maillog.0 not compressed because daemon(s) not notified

In looking at the syslog rc file, I see pidfile="/var/run/syslog.pid" 
even though the file in that folder is now /var/run/syslogd.sockets.
The second error I am a little less sure about.  Googling I saw either 
inadequate syslogd exec privilege, or a potential relation to the first 
problem?