From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.62) (envelope-from ) id 1I7O66-0008NY-Mq for garchives@archives.gentoo.org; Sun, 08 Jul 2007 04:10:11 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.14.0/8.14.0) with SMTP id l6849E58008457; Sun, 8 Jul 2007 04:09:14 GMT Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.175]) by robin.gentoo.org (8.14.0/8.14.0) with ESMTP id l6847PEb006249 for ; Sun, 8 Jul 2007 04:07:25 GMT Received: by ug-out-1314.google.com with SMTP id a2so1032599ugf for ; Sat, 07 Jul 2007 21:07:25 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Psh+IHOKjlaQplRXAhdCCvd1TDFpT2yjbEU/89kbu3vdW4xz/rMeAqYV0iU7dC+YzE+K8DgHD5XPdwX6EOfksBFJWUXXfZG5OdEYlU6R8ciNK4FTm5yCpDaPak9H4+B7+T5YCDoPupaCKNpTW2W9RuO8YNdfLxyQ61OQ+IiTpXE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=RhDgwFezGHP/aQsAJHCzAhe6nO5P0/yFzNeuufiHcfPg4ZsZ1MRxw4B3wM4kPKFnx9bp0ZKY5sCe3vmPWmFE8138Vr0wpk0HGHW/AFw2VyaCQax7lARJzG5o6TJaGoWPsQEdV/LKosuKknfsrhx1yqeupG5HU7LF9dncY7MmYeI= Received: by 10.78.180.16 with SMTP id c16mr985537huf.1183867644193; Sat, 07 Jul 2007 21:07:24 -0700 (PDT) Received: by 10.78.46.12 with HTTP; Sat, 7 Jul 2007 21:07:24 -0700 (PDT) Message-ID: <2bd962720707072107w5f9594cdl6d6183262ed103df@mail.gmail.com> Date: Sun, 8 Jul 2007 00:07:24 -0400 From: "Ryan Reich" To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Inotify and (f)crontabs In-Reply-To: <200707072321.28435.vapier@gentoo.org> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <2bd962720707010748g6fcb96cfw47a85610aadc9f79@mail.gmail.com> <200707070423.35314.vapier@gentoo.org> <1183831982.3484.1.camel@tuxhugs> <200707072321.28435.vapier@gentoo.org> X-Archives-Salt: 0d3ca48d-ff39-40bc-9fdc-84cfbdbdeb02 X-Archives-Hash: 395915a816bc99540bacc7760276f346 On 7/7/07, Mike Frysinger wrote: > On Saturday 07 July 2007, Peter Gordon wrote: > > On Sat, 2007-07-07 at 04:23 -0400, Mike Frysinger wrote: > > > you missed a critical aspect: offline time. the way run-crons is > > > implemented, if you happen to routinely shut your machine off at the time > > > that the cronjob is supposed to fire, then the standard you proposed will > > > pretty much never fire. the run-crons implementation however has a > > > pretty good guarantee that the periodic crons will get fired at the next > > > uptime opportunity. > > > > Isn't this perfectly what anacron is intended for? > > yes and no ... anacron is designed with this issue in mind, but as the > homepage of anacron explains, it does not replace the normal cron > functionality and as such cannot be used on its own I have to disagree in this particular case. The anacron homepage, anacron.sourceforge.net, gives this exact situation as its primary example of what anacron is intended for. Sure, it's not good for handling more complex scheduling, but it seems to do what run-crons tries to do: run jobs that should have been executed while the computer was off, as soon as it comes back on. Am I missing something subtle? -- Ryan Reich -- gentoo-dev@gentoo.org mailing list