[lug] KILL syslogd

[Chip Atkinson]

Check your disk space first.  It may be that you are out of space, which
causes it to go nutz.  You may also wish to check what it is doing by
looking at the files in /var/log (red hat at least).  You can find out
where by looking in /etc/syslog.conf.  If it looks like everything is ok,
sure, kill it and restart it.  You can do it as root the "smooth" way from
/etc/rc.d/init.d and run the syslog script.  Again, this is redhat
centric.

Chip

On Mon, 24 Apr 2000, Lee, David P wrote:

> I was just wondering what types of problems I would have by killing syslogd
> for a while?
> 
> It has just went on a CPU hog rampage!
> 
> Thanks
> 
> DPauL
> 
> _______________________________________________
> Web Page:  http://lug.boulder.co.us
> Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
>