Hi,
As part of cron.daily, a program called "Logwatch" is being run on osgeo1. This program is apparently analyzing system logs, and appears to be quite CPU intensive -- it used up an entire CPU for over 15 minutes, as well as a significant amount of disk activity.
Do we need this program? Is it doing anything we care about, and is it worth the cost of having the system slowdown at this time every day?
A similar question for webalizer, though this one seems less CPU intensive: are we still using webalizer?
Regards,
--
Christopher Schmidt
Nokia
On Jun 9, 2010, at 4:23 AM, ext christopher.schmidt@nokia.com wrote:
Hi,
As part of cron.daily, a program called "Logwatch" is being run on osgeo1. This program is apparently analyzing system logs, and appears to be quite CPU intensive -- it used up an entire CPU for over 15 minutes, as well as a significant amount of disk activity.
Do we need this program? Is it doing anything we care about, and is it worth the cost of having the system slowdown at this time every day?
Further investigation shows that this logwatch is configured with the default config, and is only going to the 'root' account (redirected to the 'sbarnes' account) on the OSGeo local server. I have removed logwatch from cron.daily. If we wish to re-enable it at some point, we should recreate this symlink:
lrwxrwxrwx 1 root root 28 Sep 3 2008 00-logwatch -> ../log.d/scripts/logwatch.pl
in /etc/cron.daily/
Regards,
--
Christopher Schmidt
Nokia