I like the idea of just putting a shutdown command for the coming Sunday in your startup scripts. I haven't studied Mint's startup yet. But that just seems like a plain nice idea.
But cron works too. Totally.
I think it is appropriate to put it in the root user's cron table and not the system /etc/crontab since that may be overwritten on many UNIXES.
However the table format for a user crontab is different you do not put the user
(in most cron implementation I know of anyway) and I think that is your error toddbailey
. Remove " root" it is implicit since it is root's user cron table.
If you examine the logs it may have filed an error about not finding a command named root or something like that.
When you troubleshoot a cron issue you can vet your syntax by making a test event at a convenient time in a couple of minutes from when you input it. For example,
- Code: Select all
dale@cutermaster:~$ crontab -l
no crontab for dale
Sun Oct 13 12:19:04 PDT 2013
dale@cutermaster:~$ echo '20 12 * * * echo wow | wall' | crontab
Sun Oct 13 12:19:40 PDT 2013
Broadcast Message from dale@cutermas
(somewhere) at 12:20 ...
See also the different manual sections because if you type man cron, you might actually want CRON(5) so type man 5 cron.