Bug 2917

Summary: cron.d and cron.daily
Product: [Retired] Red Hat Linux Reporter: Thomas Zehetbauer <thomasz>
Component: vixie-cronAssignee: Crutcher Dunnavant <crutcher>
Status: CLOSED WORKSFORME QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 6.0CC: pbrown
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2001-04-10 21:58:58 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Thomas Zehetbauer 1999-05-18 23:07:46 UTC
several scripts (e.g. tetex and tmpwatch) are placed in
/etc/cron.daily but I cannot find any evidence that they
ever get executed.

the format of /etc/crontab and /etc/cron.d/* is not
documented. there is just a dead reference to crontab(5) in
cron(8)

Also I want to say that I would prefer logging to be done
via syslog.

Comment 1 Derek Tattersall 1999-05-19 14:56:59 UTC
Both tetex.cron and tmpwatch scripts use tmpwatch(8) which does not
log its actions, so no evidence will be left around.

man -S 5 crontab is your friend.  /usr/bin/run-parts  is used by the
system crontab, /etc/crontab, to run the scripts in /etc/cron.daily
etc.

Your suggestion about logging  to syslogd will be passed on.