The translation is temporarily closed for contributions due to maintenance, please come back later.
The translation was automatically locked due to following alerts: Could not merge the repository.Could not update the repository.
Zen

Source string Source string

436/10000 · 436

This translation is currently locked.

English Actions
`job-identifier` — unique name referring to a particular job used in the log files
`command` — command to be executed
The command can be either a command such as [command]#ls /proc >> /tmp/proc# or a command which executes a custom script.
Any lines that begin with a hash sign (#) are comments and are not processed.
Examples of Anacron Jobs
The following example shows a simple `/etc/anacrontab` file:
SHELL=/bin/sh
PATH=/sbin:/bin:/usr/sbin:/usr/bin
MAILTO=root
# the maximal random delay added to the base delay of the jobs
RANDOM_DELAY=30
# the jobs will be started during the following hours only
START_HOURS_RANGE=16-20
#period in days delay in minutes job-identifier command
1 20 dailyjob nice run-parts /etc/cron.daily
7 25 weeklyjob /etc/weeklyjob.bash
@monthly 45 monthlyjob ls /proc >> /tmp/proc
All jobs defined in this `anacrontab` file are randomly delayed by 6-30 minutes and can be executed between 16:00 and 20:00.
The first defined job is triggered daily between 16:26 and 16:50 (RANDOM_DELAY is between 6 and 30 minutes; the `delay in minutes` property adds 20 minutes). The command specified for this job executes all present programs in the `/etc/cron.daily/` directory using the [command]#run-parts# script (the [command]#run-parts# scripts accepts a directory as a command-line argument and sequentially executes every program in the directory). See the `run-parts` man page for more information on the [command]#run-parts# script.
The second job executes the `weeklyjob.bash` script in the `/etc/` directory once a week.
The third job runs a command, which writes the contents of `/proc` to the `/tmp/proc` file ([command]#ls /proc >> /tmp/proc#) once a month.
Configuring Cron Jobs
indexterm:[cron,user-defined tasks]indexterm:[/var/spool/cron]indexterm:[cron,cron configuration file]indexterm:[crontab] The configuration file for cron jobs is `/etc/crontab`, which can be only modified by the `root` user. The file contains the following:
SHELL=/bin/bash
PATH=/sbin:/bin:/usr/sbin:/usr/bin
MAILTO=root
HOME=/
# For details see man 4 crontabs
# Example of job definition:
# .---------------- minute (0 - 59)
# | .------------- hour (0 - 23)
# | | .---------- day of month (1 - 31)
# | | | .------- month (1 - 12) OR jan,feb,mar,apr ...
# | | | | .---- day of week (0 - 6) (Sunday=0 or 7) OR sun,mon,tue,wed,thu,fri,sat
# | | | | |
# * * * * * user-name command to be executed
The first three lines contain the same variable definitions as an `anacrontab` file: `SHELL`, `PATH`, and `MAILTO`. For more information about these variables, see xref:Automating_System_Tasks.adoc#s2-configuring-anacron-jobs[Configuring Anacron Jobs].
In addition, the file can define the `HOME` variable. The `HOME` variable defines the directory, which will be used as the home directory when executing commands or scripts run by the job.
The remaining lines in the `/etc/crontab` file represent scheduled jobs and have the following format:
minute hour day month day of week username command
The following define the time when the job is to be run:
`minute` — any integer from 0 to 59
`hour` — any integer from 0 to 23
`day` — any integer from 1 to 31 (must be a valid day if a month is specified)
`month` — any integer from 1 to 12 (or the short name of the month such as jan or feb)
`day of week` — any integer from 0 to 7, where 0 or 7 represents Sunday (or the short name of the week such as sun or mon)
The following define other job properties:
`username` — specifies the user under which the jobs are run.
`command` — the command to be executed.
The command can be either a command such as [command]#ls /proc /tmp/proc# or a command which executes a custom script.
For any of the above values, an asterisk (*) can be used to specify all valid values. If you, for example, define the month value as an asterisk, the job will be executed every month within the constraints of the other values.

Loading…

User avatar None

String updated in the repository
SHELL=/bin/bash
PATH=/sbin:/bin:/usr/sbin:/usr/bin
MAILTO=root
HOME=/
# For details see man 4 crontabs
# Example of job definition:
# .---------------- minute (0 - 59)
# | .------------- hour (0 - 23)
# | | .---------- day of month (1 - 31)
# | | | .------- month (1 - 12) OR jan,feb,mar,apr ...
# | | | | .---- day of week (0 - 6) (Sunday=0 or 7) OR sun,mon,tue,wed,thu,fri,sat
# | | | | |
# * * * * * user-name command to be executed
SHELL=/bin/bash
PATH=/sbin:/bin:/usr/sbin:/usr/bin
MAILTO=root
HOME=/
# For details see man 4 crontabs
# Example of job definition:
# .---------------- minute (0 - 59)
# | .------------- hour (0 - 23)
# | | .---------- day of month (1 - 31)
# | | | .------- month (1 - 12) OR jan,feb,mar,apr ...
# | | | | .---- day of week (0 - 6) (Sunday=0 or 7) OR sun,mon,tue,wed,thu,fri,sat
# | | | | |
# * * * * * user-name command to be executed
2 years ago
Browse all string changes

Things to check

Ellipsis

The string uses three dots (...) instead of an ellipsis character (…)

Reset

Multiple failing checks

Following checks are failing:

Unchanged translation
Indonesian, Korean

Reset

Glossary

English English
No related strings found in the glossary.

11944632 String information

Source string description
type: delimited block -
Flags
no-wrap, read-only
Source string location
./pages/monitoring-and-automation/Automating_System_Tasks.adoc:230
String age
2 years ago
Last updated
a year ago
Source string age
2 years ago
Translation file
pot/f35/pages/monitoring-and-automation/Automating_System_Tasks.pot, string 75