It is usually instructed to introduce new cron jobs through command lines; but I found it easier (with a better control of current cron tasks) to manually edit (in text editor) the user cron file like /var/spool/cron/crontabs/root
.
Is it dangerous to edit the file in text editor?
The comments in the default file is confusing. The first line says
# DO NOT EDIT THIS FILE - edit the master and reinstall.
But the fourth line says
# Edit this file to introduce tasks to be run by cron.
If you modify the user file under crontabs, it should work. However, there are two issues to take into consideration:
crontab -e
command.Edit
One more point to add. When you edit the file directly, you may be warned by the text editor if you opened the file twice (two users accessing the same file). However, the cron list will be overwritten when using
crontab -e
from two different shell sessions of the same user. This is another difference.If I understand correctly, you are editing the file manually with a text editor because you don't want to use crontab -e. I'll guess that's because it's using vi as the editor and you are unfamiliar with it.
You change crontab -e (and other things that need an editor) to use the more familiar nano editor by running
before
You can make nano the permament default editor by editing your ~/.bash_profile file to include
export EDITOR=nano
at the end.To answer your question, you should not edit the file directly because it might be overwritten without you knowing it. The 4th line says what it says because it comes from the crontab that you are supposed to manually edit (it would say that as the first line).
This is the correct way to change editor for crontab.