["Greg A. Woods" <woods@weird.com>]
> [ On Tuesday, September 26, 2000 at 15:05:24 (-0700), regs@zembu.com wrote: ]
> > Subject: bin/11087: syslogd not working, HUP doesn't fix, requires hard restart
> >
> > 	Our machine has been up for a while.  About 2 weeks ago (see 
> > 	logfile excerpt) log data stop appearing the logs.  I attempted to
> > 	HUP syslog, which generated a restart line in /var/log/messages. 
> > 	Still, no log data.  A hard restart fixed it.
> 
> A "hard" restart of syslogd alone, or a full reboot of the system?

Of syslogd alone.  Sorry, I should have described the symptoms better. 

I noticed /var/log/messages was empty, save for syslogd restart messages, at
10 PM every night. (In retrospect, I also noticed that messages were not
being delivered to root, like they should have been... I didn't notice that
until after they started showing up again).

Hmm... that's odd, I think. Out of curiousity, I invoke /usr/bin/logger
with a test message.  Nothing shows up in the logs.  I check syslog.conf (I
not the only Charlie Root on this machine, so who knows what might changed)
at thorpej's suggestion... looks fine.

I kill syslogd.  I restart it. logger now works and messages are delivered
to my console.

-- 
Ari Gordon-Schlosberg <agordon@zembu.com>