>Number:         12337
>Category:       bin
>Synopsis:       syslogd creates syslog.pid, but newsyslog looks for syslogd.pid
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    bin-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Mar 05 16:55:00 PST 2001
>Closed-Date:
>Last-Modified:
>Originator:     SUNAGAWA Keiki
>Release:        current as of today
>Organization:
	Yokogawa Electric Corporation
>Environment:
	
NetBSD azarin 1.5R NetBSD 1.5R (AZARIN) #0: Sat Feb  3 08:58:53 JST 2001     kei@azarin:/b/NetBSD-cvs/src/sys/arch/macppc/compile/AZARIN macppc


>Description:
	syslogd creates /var/run/syslog.pid for its process id info, but
	newsyslog looks for /var/run/syslogd.pid.

	Here's the message from cron.

-----
	by azarin.localnet (8.11.2/8.8.8) id f25H01101684;
	Tue, 6 Mar 2001 02:00:01 +0900 (JST)
Date: Tue, 6 Mar 2001 02:00:01 +0900 (JST)
Message-Id: <200103051700.f25H01101684@azarin.localnet>
From: root (Cron Daemon)
To: root
Subject: Cron <root@azarin> /usr/bin/newsyslog

newsyslog: /var/run/syslogd.pid: No such file or directory
-----

>How-To-Repeat:

	Update /etc/rc.d/* to most recent version.
	Wait until next morning and look at the mail from cron.

>Fix:

	It's unclear for me, but creating /var/run/syslogd.pid rather than
	/var/run/syslog.pid would be more consistent with other daemons.
>Release-Note:
>Audit-Trail:
>Unformatted: