Bug 3539

Summary: cron(8) does not appear to rescan crontabs.
Product: [Retired] Red Hat Linux Reporter: bgray
Component: crontabsAssignee: Crutcher Dunnavant <crutcher>
Status: CLOSED WORKSFORME QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 6.0   
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:54 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description bgray 1999-06-17 17:45:17 UTC
Cron jobs entered via "crontab -l" don't appear to take
effect unless crond is stopped and restarted.

Comment 1 Michael K. Johnson 1999-07-13 21:00:59 UTC
"crontab -l" is for listing current jobs, not for entering
new jobs.  Do you mean "crontab <filename>" or "crontab -e",
or what?

I have tested installing a new personal crontab entry, and
crontab properly rescanned it without touching the cron daemon.