crontab’s @reboot only works for root?
man 5 crontab is pretty clear on how to use crontab to run a script on boot:
cron
Interactive shell with environment identical to cron
I am aware of a lot of pitfalls in the magic world of crontabs, but sometimes it would help troubleshooting a lot when you have some smart way to enter an interactive (bash) shell with exact identical environment as when a shell script is run from a crontab.
how to properly log the output of a console program that frequently updates “parts” of the screen, resulting in a messy log file?
I have some Java executable (jar) that is run my some shell script from a cron job once every night. That executable does not print log statements “as usual” just by printing them out in a sequential manner like line after line (print after print), but while it processes its data its printing a single line with status data and then “overwrite” or “update” just that single line over and over again, until its done with this part of processing.
Add something to crontab programmatically (over ssh)
I have a deployment script.
It must add something to a user crontab
(trigger a script that cleans logs every XXX days);
however, this must be done only during the first deployment,
or when it needs to be updated.
Why does cron silently fail to run sudo stuff in my script?
I have a script run from a non-privileged users’ crontab that invokes some commands using sudo. Except it doesn’t. The script runs fine but the sudo’ed commands silently fail.
executing a sh script from the cron
I have a test.sh script
How do I start a Cron job 1 min after @reboot?
I need my script to be executed a minute after each reboot. When I apply @reboot in my crontab it is too early for my script – I want the script to be executed after all other tasks that are routinely run on reboot. How might I run the script sometime after reboot?
BashScript works from Terminal but not from CronTab
I’ve got a bunch of CronJobs, and they work fine, except for one. I’ve looked through a lot of forums and websites, and tried a combination of things but alas nothing has worked.
Prevent systemd timer from running on startup
I’ve been migrating my crontabs to systemd’s timer units. They all look similar to this:
tput: No value for $TERM and no -T specified
I am trying to run a bash script I have via cron, and I am getting the following error at the beginning of the execution: