Scheduling Magic: Intro to Cron on Linux

You may be aware, but magic step happens in the context of the Linux operating system. Without your help or intervention, programs to start and run daemons. These things happen because Linux is an exceptional programming system called cron. You want to do some magic? Let's get to know cron.

The cron utility allows the user to manage scheduled tasks from the command line. Once a user includes how cron works, it is not difficult to use. But for some, the understanding can be a challenge. Users must understand how Linux interpreter and reads the time on a system. Also, users must know how to edit their crontab files. Once a user has a full understanding of these concepts, they will be the masters of cron. Look at cron, and how to create entries in a users crontab file '.

By default, a version of cron (there is more than one implementation) will already be installed on the Linux system, so there is not place to worry about installation of the tool. And with respect to its use, there are two commands associated with cron:

cron: the daemon which is used to run regular commands.crontab: the command used to invoke the editor to manage users cron jobs.

A users crontab file ' is the file that contains read by cron jobs. Each user on a system may have a file crontab (including the root user) where the jobs and tasks can be controlled. The system itself also has a crontab file located in/etc/crontab, but should not be changed by the user. This file is generated during the installation of the operating system. If the file/etc/crontab is examine it is revealed that she actually control cron jobs located in/etc/cron.daily, /etc/cron.weekly and/etc/cron.monthly. But this file is not going to be the focus here. Instead the user crontab file will be the main element, as is the file used for the planning of the ordinary user tasks.

One of the aspects of cron that most users to travel so far are the way that time is used. For each crontab entry a specific time is declared for when the entry will be executed. The time entry is in the form:

0 23 *.

Each entry of time consists of five sections:

Minute (0-59) hour (0-23 with 0 being 12: 00 AM) day of the month (1-31) month (1-12) day of the week (0-6 with 0 being Sunday)

If a typical entry might look like:

Minute hour day mtee dayOfWeek

Some examples of time:

0 23 * Every day at 11 PM

30 22 * Every day at 10: 30 am

23 0 1 * Each first day of the month at 11 am

0 23 * 0 Each Sunday at 11 A.m.

Now that time is included, it is time to start adding entries. To view a users crontab file ' the crontab command is invoked. There are three main options for use with the crontab command:

e: Edit the crontab file.l: list the contents of the file.r of crontab: delete the contents of the crontab file.

Where the crontab-l command is invoked for crontab users file entries will be poster (if applicable). To add an entry to the crontab file a users', the EI crontab command is invoked for the crontab file will be opened in the default editor (such as ed, vim.tiny or nano). When the command of e - crontab is executed for the first time, the default editor is defined. To select the default editor for crontab, select the number that corresponds to the desired Editor.

Figure 1 shows a crontab entry created by the backup application Luckybackup .

A crontab open, with Nano as editor by default, showing the Luckybackup entry.

To illustrate how add a new entry in crontab, a simple backup script will be used. The contents of this script might look like:

#! / bin/bash
echo backup begins "date" > ~/backuplog
mkdir/media/EXT_DRIVE/backup /'date + % Y % m % of
tar - czf/media/EXT_DRIVE/backup /'date of telecommunications +%Y%m%d'/data.tar.gz
echo completed backup "date" > ~/backuplog

Where EXT_DRIVE is the location of an external connection drive where the backup data will reside.

The above script is saved in the directory of users such as. my_backup.sh and executable permission with the command chmod u + x ~ /. my_backup.sh. Now, with crontab in edit mode, create an entry that will allow to run the script every night at 11 pm, add the following line:

* 23 * ~/.my_backup.sh

With the entry into force, save and close the editor (will depend how it's done on the default editor that you chose). When this is done, as long as there are no errors, crontab will report "crontab: installing new crontab" to indicate the entry has been successful. If there are errors, open the file crontab back up to make the necessary changes.

Say that a different users crontab should be edited. It is not necessary to su to this different user, as crontab has an option built in for that specific purpose. If crontab is issued using the u - like crontab EI u user name, the crontab file of the specified user (where username is the user in question) will be opened for editing. This command, however, can only be issued by a user with the administrative user (or the command can be issued using sudo). Of course, editing crontab files other users should be limited to administrators.

The cron system helps make Linux one of the operating systems more flexible around. Cron allows not only the system keep its logs a rotation and clean, it allows users to set their own tasks, scripts, and jobs. Although the aspect of time cron can be a little difficult to understand, once it is understood, the rest falls into place.

If the idea of modifying entries cron for command line seems a little much, you'll be glad to know there are GUI tools for this task. Take a look at a such tool GNOME schedule (found in your Add/Remove software tool) for an application that can manage your tasks cron with the help of user-friendly graphical interface. But for those who want to really understand Linux, familiar with cron and crontab is essential.

Comments (1)
You must be logged on to post a comment. Please register if you do not yet have an account.

View the original article here

This post was made using the Auto Blogging Software from WebMagnates.org This line will not appear when posts are made after activating the software to full version.