Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Not sure if you're overlooking something, but here is how I handle mine on Slackware 10.1 (running 'crontab -e' doesn't work for me - something to do with my editor settings).
As root I do the following:
vi cron_holder (make entries/edits, save changes)
This creates a cron.update file in the same directory that gets processed on the next cron cycle (not sure if I'm explaining it right) and copies your changes into the 'root' file which is run by cron - editing the 'root' file directly is a bad idea and the changes won't go into affect.
Thanks to everyone for their help but the problem fixed itself. I woke this morning and started the computer and the cron job ran. I changed nothing from last night. My guess is the cron dameon wasn't working last night but did work this morning after booting. Why it was'nt working last night is beyond me though.
Distribution: Red Hat (8.0, RHEL5,6), CentOS, SuSE (10.x, 11.x, 12.2, 13.2), Solaris (8-10), Tru64, MacOS, Raspian
Re: cron problems
Hi, I am trying to synchronize my clock every hour through a cron job.
Am I overlooking anything?
I'm wondering whether setting up the NTP service wouldn't be easier than the cron job. Yes, you do need to track down a suitable time server (see the lists on http://ntp.isc.org/bin/view/Servers/WebHome) but once that's done it's pretty much "set and forget".