I've been taking a look at how RedHat (and CentOS) handles logrotate. According to the man page, logrotate is supposed to be fired by cron. But when I look at root's crontab $ sudo crontab lu root no crontab for root What exactly fires logrotate (and other scheduled events like "logwatch", which ends up in root's inbox)? === Al
On Aug 21, 2008, at 2:06 PM, Al Sparks wrote:> What exactly fires logrotate (and other scheduled events like > "logwatch", which ends up in root's inbox)?look at /etc/cron.daily/logrotate and /etc/cron.daily/0logwatch. those scripts (and the others in /etc/cron.*ly) are invoked by the following code in /etc/crontab: # run-parts 01 * * * * root run-parts /etc/cron.hourly 02 4 * * * root run-parts /etc/cron.daily 22 4 * * 0 root run-parts /etc/cron.weekly 42 4 1 * * root run-parts /etc/cron.monthly -steve -- If this were played upon a stage now, I could condemn it as an improbable fiction. - Fabian, Twelfth Night, III,v
On Thu, Aug 21, 2008 at 11:06:19AM -0700, Al Sparks wrote:> I've been taking a look at how RedHat (and CentOS) handles logrotate. > According to the man page, logrotate is supposed to be fired by cron. > But when I look at root's crontab > $ sudo crontab lu root > no crontab for rootSee /etc/cron.daily (see also other directories matching /etc/cron.*) Look in /etc/crontab to see how they're called. -- rgds Stephen
On Thu, 21 Aug 2008 at 11:06am, Al Sparks wrote> I've been taking a look at how RedHat (and CentOS) handles logrotate. > According to the man page, logrotate is supposed to be fired by cron. > But when I look at root's crontab > $ sudo crontab lu root > no crontab for root > > What exactly fires logrotate (and other scheduled events like > "logwatch", which ends up in root's inbox)?Look in /etc/cron.{hourly,daily,monthly,weekly}. -- Joshua Baker-LePain QB3 Shared Cluster Sysadmin UCSF