Re: cron jobs more often than daily
- To: Debian Development <email@example.com>
- Subject: Re: cron jobs more often than daily
- From: Christian Schwarz <firstname.lastname@example.org>
- Date: Tue, 6 Jan 1998 11:49:30 +0100 (CET)
- Message-id: <Pine.LNX.3.96.980106114024.23176E-100000@monet>
- In-reply-to: <19980106022826.03743@kite>
I currently see three practical solutions out of the dilemma (that
/etc/crontab is edited by the sysadmin and scripts):
(a) We set up another crontab (say /etc/crontab.deb) which is maintained
by install-cronjob only. The current /etc/crontab will stay a
conffile and only be touched by the sysadmin.
Disadvantage: The sysadmin might want to remove (or change) an entry
of /etc/crontab.deb too, so we didn't solve any problems.
(b) We set up a certain directory (say /usr/lib/cronjobs) where each
package can install its own crontab file (/usr/lib/cronjobs/foo).
Disadvantage: See above.
(c) We split /etc/crontab into two "areas". The install-cronjob script
will only touch one area, while the sysadmin can touch both. For
# Sysadmin's private area: Do whatever you like to do here.
# Nothing will be changed automatically...
* * * * * root rm -rf /
# (I hope noone installs this crontab :)
# automatic area: You can do changes to this area, but packages
# might add or remove new entries via install-cronjob
# ---entry from package foo1---
* * * * * root something
# ---entry from package foo2---
This keep all cronjobs in a single file which makes life easier for
the sysadmin, I think.
Note, that the install-cronjob script should be smart enough to
handle commented-out cron entries correctly (they should stay
commented-out during package upgrades).
-- Christian Schwarz
Debian has a logo! email@example.com, firstname.lastname@example.org
Check out the logo PGP-fp: 8F 61 EB 6D CF 23 CA D7 34 05 14 5C C8 DC 22 BA
pages at http://fatman.mathematik.tu-muenchen.de/~schwarz/debian-logo/
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
Trouble? e-mail to email@example.com .