diff options
author | Robby Workman <rworkman@slackbuilds.org> | 2021-04-21 22:37:38 -0500 |
---|---|---|
committer | Robby Workman <rworkman@slackbuilds.org> | 2021-04-21 22:37:38 -0500 |
commit | 39075e3be801d920f8ee52dc81f05ded1a4bfae7 (patch) | |
tree | 68021bb6f41252048df865d42c5addd4081d8cb5 /system/anacron/README | |
parent | 519a4313931f4c380d4966ce5a5210760b4687e1 (diff) |
system/anacron: Removed (no maintainer)
Diffstat (limited to 'system/anacron/README')
-rw-r--r-- | system/anacron/README | 36 |
1 files changed, 0 insertions, 36 deletions
diff --git a/system/anacron/README b/system/anacron/README deleted file mode 100644 index 733c9630877d5..0000000000000 --- a/system/anacron/README +++ /dev/null @@ -1,36 +0,0 @@ -anacron (periodic command scheduler) - -anacron is a periodic command scheduler. It executes commands at -intervals specified in days. Unlike cron, it does not assume that the -system is running continuously. It can therefore be used to control -the execution of daily, weekly and monthly jobs (or anything with a -period of n days), on systems that don't run 24 hours a day. When -installed and configured properly, Anacron will make sure that the -commands are run at the specified intervals as closely as -machine-uptime permits. - -Every time Anacron is run, it reads a configuration file that -specifies the jobs Anacron controls, and their periods in days. If a -job wasn't executed in the last n days, where n is the period of that -job, Anacron executes it. Anacron then records the date in a special -timestamp file that it keeps for each job, so it can know when to run -it again. When all the executed commands terminate, Anacron exits. - -It is recommended to run Anacron from the system boot-scripts. For -example, add the following lines to /etc/rc.d/rc.local: - - if [ -x /usr/sbin/anacron -a -f /etc/anacrontab ]; then - /usr/sbin/anacron -s > /dev/null 2>&1 - fi - -This way the jobs "whose time has come" will be run shortly after the -machine boots. A delay can be specified for each job so that the -machine isn't overloaded at boot time. - -In addition to running Anacron from the boot-scripts, it is also -recommended to schedule it as a daily cron-job (usually at an early -morning hour), so that if the machine is kept running for a night, -jobs for the next day will still be executed. - -See anacron (8), anacrontab (5) and /usr/doc/anacron-2.3/README -for further information. |