DebianThis forum is for the discussion of Debian Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
# m h dom mon dow user command
30 * * * * root /usr/local/FWTools-1.1.3/bin_safe/goastro
30 * * * * root run-parts --report /etc/cron.hourly
25 6 * * * root test -x /usr/sbin/anacron || run-parts --report /etc/cron.daily
47 6 * * 7 root test -x /usr/sbin/anacron || run-parts --report /etc/cron.weekly
52 6 1 * * root test -x /usr/sbin/anacron || run-parts --report /etc/cron.monthly
#
But it never runs. My old Debian Sarge machine worked fine. What's the problem? The script goastro is a bash script with a+x permissions. I'm logged in to Gnome as regular user, but edit crontab as root. Please help figure out why crontab does not start goastro.
I've aslo tried to crontab -e and put in spooler but that won't go either. crontab -l gives the correct info for root.
They both do the same thing just a different way of writing it. $PATH is a shortcut your normal environment variable that should include what you have there. If you need another path just tack it onto the end.
There is no /var/log/cronrun logfile. Also there is no /etc/cron.allow or /etc/cron.deny
Here is my current complete crontab:
# /etc/crontab: system-wide crontab
# Unlike any other crontab you don't have to run the `crontab'
# command to install the new version when you edit this file.
# This file also has a username field, that none of the other crontabs do.
OK, I have a part of the problem figured out.
Crontab jobs run according to local time.
My jobs are scheduled for specific hours based on UT (GMT).
I use UT because my scripts get worldwide forecast data, which are based on UT and issued at the hours 0UT, 6UT, 12UT, 18UT.
My clock in Gnome is set for 24 hour UT time format but cron was using local time. The solution was change the crontab schedule to local time.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.