Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

If I (e.g.: under Fedora) edit the crontab file with vim, then I restart crond:

/etc/init.d/crond restart

then the actual crontab file: "/etc/crontab" is the same as the actual cronjobs in reality. Ok!

Q: How could I list the real-actual cronjobs, if the "/etc/crontab" file gets modified, but the crond not reloaded? Then the real-actual cronjobs aren't the same as the "/etc/crontab" file.
Thank you!

share|improve this question
up vote 1 down vote accepted

All the implementations of cron that I know of re-read /etc/crontab every minute, i.e. as often as they execute jobs. So the “real-actual” cron jobs are the ones in the crontab file.

There are (or were) a few buggy implementations of cron that check for jobs to execute first and only then check the crontabs. This causes one minute's delay between setting the jobs and running them. I don't think any of the current cron implementations on Linux (there are several) are affected.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.