Danny Sauer wrote:
Paul wrote regarding 'Re: [SLE] crontab' on Fri, Oct 15 at 21:16:
That will work, of course, but I find it more convenient to create a crontab in a local file ~/mycrontab (in this case /home/root/mycrontab) and then do: crontab ~/mycrontab crontab -l # check that it worked
Doesn't that command replace the current crontab with the one specified on the command line? Wouldn't it be easier just to run "crontab -e", which starts up the editor specified by $EDITOR, rather than starting up the editor, saving a file, and then running crontab on that file? Seems like you're adding some extra steps to the process...
Eh, I guess "There's More Than One Way To Do It". Whatever works. :)
--Danny
Danny, in this case remember to read your command line before pressing enter; just to check if you get "crontab -r" instead of "crontab -e" - R and E keys are 'neighbors keys', and you'll get almost *opposite* behavior in each case... :-) I never did that, but saw a friend suffering from such mistake -- Marcos Lazarini