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.
I'm wondering what the best method is under Linux (Fedora Core 1) to set up some set jobs to run every day. Here's what I want the job to do:
1. Stop the MySQL service.
2. Compress the /var/lib/mysql folder into a single RAR file.
3. Start the MySQL service as soon as the archive is created.
4. Move the archive to a network folder.
Each of these are easy on their own. I want to have a single job that does each of these in turn. I'm aware of Cron, but I'm not sure how to get it to run something like this. As far as I know, I would have to specify the time of day I want each job part to run. I don't know how long the creating of the archive will take, and it will vary depending on how big the databases are. I can't very well have the service trying to start and modify the tables while they are being compressed.
So, I'm hoping someone can suggest a method to run each of the steps above in order, as soon as the previous step completes so I don't have to specify a time for each.