Bug 3539 - cron(8) does not appear to rescan crontabs.
cron(8) does not appear to rescan crontabs.
Status: CLOSED WORKSFORME
Product: Red Hat Linux
Classification: Retired
Component: crontabs (Show other bugs)
6.0
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Crutcher Dunnavant
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 1999-06-17 13:45 EDT by bgray
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2001-04-10 17:58:54 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description bgray 1999-06-17 13:45:17 EDT
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 17:00:59 EDT
"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.

Note You need to log in before you can comment on or make changes to this bug.