cronjob entry in crontab -e vs /etc/crontab . Which one is better?
The difference is that the crontab
command is the interface provided by the system for users to manipulate their crontabs. The /etc/crontab
file is a special case file used to implement a system-wide crontab. /var/spool/cron/crontabs/$USER
(or whatever the path happens to be) is an implementation detail.
If you can schedule jobs using the crontab
command, you should do so.
Manually editing the contents of /etc/crontab
(a) requires root access, and (b) is more error-prone. You can mess up your system that way.
If the jobs are to be run under your own user account, there's no need to use root access.
Even if the jobs are to run as root
, it probably still makes more sense to use the crontab
command invoked from the root
account. (For one thing, it should detect syntax errors in the file.)
Personally, I don't use crontab -e
. Instead, I have a crontab file that I keep in a source control system, and I use the crontab filename
form of the command to install it. That way, if I mess something up, it's easy to revert to an earlier version.
Ameyj
Updated on June 05, 2022Comments
-
Ameyj almost 2 years
What is the difference when I put crontab entry in crontab -e (the default location is : /var/spool/cron/username ) and in /etc/crontab? I mean crond daemon will essentially execute both cron jobs. Then why there are two different ways to schedule cronjob ? Which one preferred over the other ?
-
Jesse Nickles over 4 yearsBut if using
crontab filename
to install, and you're sure the code is fine, it doesn't really matter which of those 2 crontabs you are overwriting, as far as I know. -
Keith Thompson over 4 years@jessuppi It certainly does matter.
crontab filename
will always update your personal crontab (even if you run it asroot
), never/etc/crontab
. The two crontabs use different syntaxes./etc/crontab
has an extra column specifying the user to run the command. -
Jesse Nickles over 4 years@KeithThompson Those are 2 great points... maybe you can update your answer to remind users of that? In our SlickStack project (FOSS), we use the
root
user crontab as there seems to be a long-held belief that/etc/crontab
is holy and untouchable, and might one day be used by Linux distros for something system-related. Although theroot
user crontab path is a bit convoluted... -
Keith Thompson over 4 years@jessuppi: Why do you care about the path of the
root
user crontab? You should only manipulate it via thecrontab
command. -
Jesse Nickles over 4 years@KeithThompson I understand and do mate, but messy paths are never fun.
-
Keith Thompson over 2 years@JesseNickles Messy paths are neither fun nor not fun if you ignore them, and you should. I use crontab all the time, and I honestly don't know where the crontab file is stored (though I could find out easily enough).