Re: cron jobs more often than daily
Hamish Moffatt writes:
> On Mon, Jan 05, 1998 at 01:35:08PM +0100, Martin Schulze wrote:
> > On Mon, Jan 05, 1998 at 11:31:09PM +1100, Hamish Moffatt wrote:
> > > On Mon, Jan 05, 1998 at 01:26:56PM +0100, Martin Schulze wrote:
> > > > Why not add a job like:
> > > > */15 * * * * root /usr/sbin/ipac-cron
> > > > to /etc/crontab? The predecessor of at has done this, too.
> > >
> > > Policy 2.3.0.1 says
> > > Packages may not touch the configuration file `/etc/crontab', nor ma
>y
> > > they modify the files in `/var/spool/cron/crontabs'.
> > > Doesn't this rule this out?
> >
> > Oups. Well, rules exist for breaking them... An old idiom...
> > Then your only chance is to write an ipacd that forks, lets the daughter
> > call the ipcac-cron script , waits 15 mins and forks again. Started
> > via /etc/init.d/ipac.
>
> Urgh, I hate it already. Can somebody post a rationale for
> the section of policy quoted above? I notice that mgetty
> has added faxrunq to my /etc/crontab on my bo system.
Maybe because if the admin changes the /etc/crontab, it might be difficult
to merge in the modifications.
We have cron.{month,week,dai}ly, why not add directories hourly, bihourly
(every 30min), and quarterly (every 15min). That would give enough
resolution for most daemons.
I'd rather use cron for timing than daemon's built-in functionality:
- less swapped-out daemons
- more flexible configuration
-Topi
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-devel-request@lists.debian.org .
Trouble? e-mail to templin@bucknell.edu .
Reply to: