1. You have checked your log files to make sure there wasn't a lot of data
logged into them when this happens.
2. Restarting syslogd doesn't mysteriously cause this not to happen the next
hour.
You could kill syslogd, and restart it in debug mode (-d option) on a spare
xterm or whatever. It then won't fork into the background and will display any
incoming packets and what it did with them. You could look at that and see if
something is logging alot of stuff that syslog as been told not to log to a
file. With that, you can either figure out what the problem is or figure out
what the facility and priority the stuff is getting logged at, and modify you
syslog.conf to log it. Then read the log the next hour and figure out what is
going on.
On 16-Aug-99 Gregory P Whalin wrote:
> I thought this as well, but have nothing run hourly in my crontab (or anyone
> elses). Besides, I don't see how a crontab entry would cause syslogd to
> suddenly start sucking 100% of the cpu?
>
> Greg
> --
> Gregory Whalin
> gwhalin@numerix.com
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/