Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then 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.
I have just installed CentOS4 on a computer that will run as a SMB server for my dad's chemistry research group. Yesterday, I downloaded a simple backup program, backerupper, that uses cron scheduling to schedule backups at 12:10 AM each day. As I was reading the help file it says that run the setup script, backerupper.start, that moves the program binary to /etc and writes cron scripts to /var/spool/cron/crontabs/cron.update and /var/spool/cron/crontabs/root. Before I ran the setup script, I stopped the crond service and browsed to [b]/var/spool/cron. I found that there was no crontabs folder, thus no cron.update and root files there either. I created the folder crontabs in /var/spool/cron and inside the crontabs folder, I created the two files, cron.update and root. After that I ran the script, backerupper.start, I saw that it wrote 10 0 * * * /usr/local/bin/backerupper 1> /dev/null 2> /dev/null sucessfully to the root file and wrote root to the cron.update file. After that, I started the cron service back up, logged off the computer and went to bed. This morning I check to see if the program backed up to /backup and it didn't. Does anyone know what might be wrong?
If you run the command manually (just run /usr/local/bin/backerupper from the console) does it function as intended? Also, look in your logs in /var/log to see if there are entries logged from the crond.
I have checked the logs and there are a bunch of entries for crond that say session opened, session closed for user root. None of these entries though are at the times that I had specified the job to run in crontab.