wok
annotate anacron/description.txt @ rev 20283
security fixes from 0.3.1.9 (2017 Dec 1) and 0.3.1.10 (March 3)... further info: https://blog.torproject.org/new-stable-tor-releases-security-fixes-and-dos-prevention-03210-03110-02915
| author |
Erkan Yilmaz <erkan@slitaz.org> |
| date |
Tue Mar 27 11:09:07 2018 +0000 (2018-03-27) |
| parents |
|
| children |
|
| rev |
line source |
|
hackdorte@20007
|
1 Anacron is a periodic command scheduler. It executes commands at intervals
|
|
hackdorte@20007
|
2 specified in days. Unlike cron, it does not assume that the system is running
|
|
hackdorte@20007
|
3 continuously. It can therefore be used to control the execution of daily,
|
|
hackdorte@20007
|
4 weekly and monthly jobs (or anything with a period of n days), on systems
|
|
hackdorte@20007
|
5 that don't run 24 hours a day. When installed and configured properly,
|
|
hackdorte@20007
|
6 Anacron will make sure that the commands are run at the specified intervals
|
|
hackdorte@20007
|
7 as closely as machine-uptime permits.
|
|
hackdorte@20007
|
8
|
|
hackdorte@20007
|
9 Every time Anacron is run, it reads a configuration file that specifies the
|
|
hackdorte@20007
|
10 jobs Anacron controls, and their periods in days. If a job wasn't executed in
|
|
hackdorte@20007
|
11 the last n days, where n is the period of that job, Anacron executes it.
|
|
hackdorte@20007
|
12 Anacron then records the date in a special timestamp file that it keeps for
|
|
hackdorte@20007
|
13 each job, so it can know when to run it again. When all the executed commands
|
|
hackdorte@20007
|
14 terminate, Anacron exits.
|