Re: [vox-tech] cron - not at a different time (fwd)

["Karsten M. Self" <kmMAPSself@ix.netcom.com>]

on Wed, Mar 03, 2004 at 03:56:05PM -0800, Jeff Newmiller (jdnewmil@dcn.davis.ca.us) wrote:
> I accidentally sent this only to Peter... here it is for the record:
> 
> On Wed, 3 Mar 2004, Peter Jay Salzman wrote:
> 
> > On Wed 03 Mar 04, 12:04 PM, Jeff Newmiller <jdnewmil@dcn.davis.ca.us> said:
> 
> [...]
> 
> > > If cron and anacron are both installed in Debian, /etc/crontab is
> > > configured to skip daily/weekly/monthly processing, because
> > > /etc/anacrontab specifies those as well, and if your machine is regularly
> > > shut down, then anacron is better suited to handle it.  What burns me is
> > > that one _or_ the other should be installed...  someone must have decided
> > > that cron was good for some things and anacron good for others and wanted
> > > both installed... leaving you erroneously thinking you were having some
> > > effect by editing the daily entry in /etc/crontab.
> > > 
> > > In their defense, though, the solution _is_ right there in the line you
> > > edited...
> >  
> > i'm still don't understand -- how does anacron know when, that is the
> > *time* (not the date) to run?
> 
> This puzzled me too.. thanks to Steve Wormley for pointing me to the
> solution:
> 
> Vixie cron processes three sets of crontabs... /etc/crontab, individual
> crontabs (/var/spool/cron/username), and any crontabs found in
> /etc/cron.d/.  anacron is invoked periodically by a line in
> /etc/cron.d/anacron, and uses the period specs in /etc/anacrontab and
> last-executed timestamps in /var/spool/anacron/* to determine whether
> enough time has passed that it should invoke the daily/weekly/monthly
> processing.

    less /usr/share/doc/cron/README.anacron

Peace.

-- 
Karsten M. Self <kmself@ix.netcom.com>        http://kmself.home.netcom.com/
 What Part of "Gestalt" don't you understand?
   Geek for hire:  http://kmself.home.netcom.com/resume.html

Attachment: signature.asc
Description: Digital signature