Check to see if syslogd is running. If it is not running, there will be no
/etc/syslog.pid file.
Jeff
------------------------------------------------------------------------------
Dr. Jeff Masters (jmasters@xxxxxxxxxxxxxxxx) ( )
Chief Meteorologist /\ Home of the ( )
The Weather Underground, Inc. /\ / \ /\ /\ ( )
300 N Fifth Ave #240 / \/ \/ \ /\ / \ ------
Ann Arbor, MI 48104 ______/ / \/ \_ \\\\\
734-994-8824 (voice) Weather Underground \`\`\
734-994-8919 (fax) http://www.wunderground.com
On Fri, 16 Mar 2001, Chris Novy wrote:
> I'm receiving the following error upon starting LDM (5.1.2):
>
> hupsyslog: couldn't open /etc/syslog.pid
>
> It started after a bad shutdown the other day. LDM is still processing
> files OK but I also receive an error message from the newlog routine:
>
> Your "cron" job on delyte
> /usr/LDM/ldm/bin/ldmadmin newlog
>
> produced the following output:
>
> hupsyslog: couldn't open /etc/syslog.pid
>
> Any idea of what got erased or made inaccessible?
>
> ..Chris..
>
