View Single Post
Old 04-17-2016, 10:44 AM   #6
eschwartz
Ex-Helpdesk Junkie
eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.
 
eschwartz's Avatar
 
Posts: 19,421
Karma: 85400180
Join Date: Nov 2012
Location: The Beaten Path, USA, Roundworld, This Side of Infinity
Device: Kindle Touch fw5.3.7 (Wifi only)
It would be fair to say that I shouldn't be assuming /bin/sh is the symlink to bash that it should be hence the syntax error for using bash constructs.

But the "no crontab for root" error is because it prints out the current crontab, echoes the new cron job, and installs the new crontab -- there is no "append this, please" mode.
You can check that by running `sudo crontab -l` to check the current crontab. It should be there.

...

I fixed that by piping the stderr for the initial crontab -l to /dev/null, and switching the instructions to use bash.

Last edited by eschwartz; 04-17-2016 at 10:46 AM.
eschwartz is offline   Reply With Quote