From owner-freebsd-stable@FreeBSD.ORG Mon Nov 20 22:53:39 2006 Return-Path: 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 4980316A4FB for ; Mon, 20 Nov 2006 22:53:39 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from sccrmhc15.comcast.net (sccrmhc15.comcast.net [63.240.77.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id F2C3743DB6 for ; Mon, 20 Nov 2006 22:52:15 +0000 (GMT) (envelope-from jdc@koitsu.dyndns.org) Received: from icarus.home.lan (c-67-174-220-97.hsd1.ca.comcast.net[67.174.220.97]) by comcast.net (sccrmhc15) with ESMTP id <2006112022521701500psk29e>; Mon, 20 Nov 2006 22:52:17 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id EA9FF1FA01D; Mon, 20 Nov 2006 14:52:16 -0800 (PST) Date: Mon, 20 Nov 2006 14:52:16 -0800 From: Jeremy Chadwick To: Brian Message-ID: <20061120225216.GA49353@icarus.home.lan> Mail-Followup-To: Brian , freebsd-stable@freebsd.org References: <45622EEC.6030907@sonicboom.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <45622EEC.6030907@sonicboom.org> X-PGP-Key: http://jdc.parodius.com/pubkey.asc User-Agent: Mutt/1.5.13 (2006-08-11) Cc: freebsd-stable@freebsd.org Subject: Re: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Nov 2006 22:53:39 -0000 On Mon, Nov 20, 2006 at 02:40:44PM -0800, Brian wrote: > 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? Seems to me the problem has to do with syslogd not running when newsyslog attempts to send syslog a signal (hence why newsyslog is trying to read /var/run/syslog.pid). A system with a running syslogd has this in /var/run: -rw------- 1 root wheel 3 30 Oct 22:00 syslog.pid -rw-r--r-- 1 root wheel 36 30 Oct 22:00 syslogd.sockets It sounds like syslogd on your box may have died off for some reason prior to newsyslog running to do log rotation. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |