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 1I7Ep9-0005hh-BK for garchives@archives.gentoo.org; Sat, 07 Jul 2007 18:16:03 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.14.0/8.14.0) with SMTP id l67IF4fG008086; Sat, 7 Jul 2007 18:15:04 GMT Received: from spaceymail-a2.g.dreamhost.com (mailbigip.dreamhost.com [208.97.132.5]) by robin.gentoo.org (8.14.0/8.14.0) with ESMTP id l67ID4ge005755 for ; Sat, 7 Jul 2007 18:13:04 GMT Received: from [172.16.1.34] (adsl-68-121-241-160.dsl.irvnca.pacbell.net [68.121.241.160]) by spaceymail-a2.g.dreamhost.com (Postfix) with ESMTP id 92A9A109FB6 for ; Sat, 7 Jul 2007 11:13:03 -0700 (PDT) Subject: Re: [gentoo-dev] Inotify and (f)crontabs From: Peter Gordon To: gentoo-dev@lists.gentoo.org In-Reply-To: <200707070423.35314.vapier@gentoo.org> References: <2bd962720707010748g6fcb96cfw47a85610aadc9f79@mail.gmail.com> <200707070423.35314.vapier@gentoo.org> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-GkDZZdEhbjeCddOJPums" Organization: Gentoo Linux Date: Sat, 07 Jul 2007 11:13:02 -0700 Message-Id: <1183831982.3484.1.camel@tuxhugs> 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 X-Mailer: Evolution 2.11.4 (2.11.4-2.fc8) X-Archives-Salt: 2f5c9d26-acc1-4ed2-b9f0-8ac6402907da X-Archives-Hash: c8497d42a601ca1f3ad6ddb99b07bac1 --=-GkDZZdEhbjeCddOJPums Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Sat, 2007-07-07 at 04:23 -0400, Mike Frysinger wrote: > you missed a critical aspect: offline time. the way run-crons is impleme= nted,=20 > if you happen to routinely shut your machine off at the time that the cro= njob=20 > is supposed to fire, then the standard you proposed will pretty much neve= r=20 > fire. the run-crons implementation however has a pretty good guarantee t= hat=20 > the periodic crons will get fired at the next uptime opportunity. Isn't this perfectly what anacron is intended for? --=20 Peter Gordon (codergeek42) Gentoo Forums Global Moderator GnuPG Public Key ID: 0xFFC19479 / Fingerprint: DD68 A414 56BD 6368 D957 9666 4268 CB7A FFC1 9479 My Blog: http://thecodergeek.com/blog/ --=-GkDZZdEhbjeCddOJPums Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) iD8DBQBGj9eqQmjLev/BlHkRAsFzAKCM+TcwXddEitrcjha5MS14W+pQbwCdGJTc RbVcbj5VUk/bEY2dgAVf2Dg= =sdNo -----END PGP SIGNATURE----- --=-GkDZZdEhbjeCddOJPums-- -- gentoo-dev@gentoo.org mailing list