SlackwareThis Forum is for the discussion of Slackware 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.
As root I typed crontab -e and typed in the following:
Quote:
#Run rdate every Wednesday at 4:30 to keep clock accurate:
30 4 * * 3 /usr/bin/rdate -s time.nrc.ca 1> /dev/null
Will this work? Or did I leave something off? I notice that some of the other entries in crontab -e are like this:
Quote:
# Run monthly cron jobs at 4:20 on the first day of the month:
20 4 1 * * /usr/bin/run-parts /etc/cron.monthly 1> /dev/null
I notice there is an additional part in that entry that reads "/etc/cron.monthly". Do I need to add something like that to the entry I made?
I want rdate to update my system time every Wednesday at 4:30am, regardless of whether a user is logged in or not. Should I use root's crontab -e for that, or should I put an entry in /etc/cron.weekly in order to make this systemwide?
I think that will work. But if you really want to keep your clock accurate perhaps you should look into running ntp. It'll allow you to connect to a few (I recommend 3 or 4) clock servers and it'll keep your clock inline all the time. It also makes changes gradually by dropping seconds here and there until it is correct to ensure you don't run into clock skew problems with anything.
The command looks like:
ntpdate ntp.timeserver.org
Find a suitable public secondary NTP server near you, don't try syncing to a primary server, these are not intended for individuals
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.