From owner-freebsd-current  Fri Jan  3 22:02:16 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id WAA02318
          for current-outgoing; Fri, 3 Jan 1997 22:02:16 -0800 (PST)
Received: from who.cdrom.com (who.cdrom.com [204.216.27.3])
          by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id WAA02281
          for <current@FreeBSD.ORG>; Fri, 3 Jan 1997 22:02:10 -0800 (PST)
Received: from nexgen.HiWAAY.net (max7-113.HiWAAY.net [208.147.147.113])
          by who.cdrom.com (8.7.5/8.6.11) with ESMTP id SAA03680
          for <current@freebsd.org>; Fri, 3 Jan 1997 18:29:34 -0800 (PST)
Received: from nexgen.HiWAAY.net (localhost [127.0.0.1]) by nexgen.HiWAAY.net (8.7.6/8.7.3) with ESMTP id TAA06235; Fri, 3 Jan 1997 19:56:05 -0600 (CST)
Message-Id: <199701040156.TAA06235@nexgen.HiWAAY.net>
X-Mailer: exmh version 1.6.9 8/22/96
To: Randy DuCharme <randyd@nconnect.net>
Cc: current@FreeBSD.ORG
From: dkelly@hiwaay.net
Subject: Re: syslogd failure 
In-reply-to: Message from Randy DuCharme <randyd@nconnect.net> 
   of "Fri, 03 Jan 1997 17:54:32 CST." <32CD9C38.41C67EA6@nconnect.net> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 03 Jan 1997 19:56:05 -0600
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> Greetings,
> 
> Every morning Cron sends me mail about being unable to restart syslogd.  
> He says " could not restart syslogd: No such process"
> 
> Manually attempting to start 'syslogd' says "child pid xxx exited with
> return code 1"
> 
> Syslog -d says "cannot create /var/run/log: Address already in use
> logmsg: pri 53, flags 4, from arabian, msg syslogd: cannot create
> /var/run/log: Address already in use
> Logging to CONSOLE /dev/console
> cannot create /var/run/log (0)
> 
> I'm confused.  Permissions look right.  Any help would be GREATLY
> appreciated.

Yeah! Me too. Same thing was happening on my -current box. And I wasn't 
logging to /var/log/messages as a result. What really bugged me was the 
fact I got the error message mailed to me every day at 1300. Eventually I 
learned something about how -current differs from 2.1.5R in the way it 
rotates logs.

Don't know why, but "rm /var/run/log" and restarting syslogd fixed the 
problem. Did my filesystem get dirty somehow?

--
David Kelly N4HHE, dkelly@hiwaay.net
=====================================================================
The human mind ordinarily operates at only ten percent of its
capacity -- the rest is overhead for the operating system.