Date: Mon, 20 Nov 2006 14:52:16 -0800 From: Jeremy Chadwick <koitsu@FreeBSD.org> To: Brian <bri@sonicboom.org> Cc: freebsd-stable@freebsd.org Subject: Re: 6.2 rc file problems Message-ID: <20061120225216.GA49353@icarus.home.lan> In-Reply-To: <45622EEC.6030907@sonicboom.org> References: <45622EEC.6030907@sonicboom.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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 |
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20061120225216.GA49353>