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 <gentoo-dev+bounces-24820-garchives=archives.gentoo.org@gentoo.org>)
id 1I7XCE-0006nz-U9
for garchives@archives.gentoo.org; Sun, 08 Jul 2007 13:53:07 +0000
Received: from robin.gentoo.org (localhost [127.0.0.1])
by robin.gentoo.org (8.14.0/8.14.0) with SMTP id l68Dq8Ed022803;
Sun, 8 Jul 2007 13:52:08 GMT
Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.174])
by robin.gentoo.org (8.14.0/8.14.0) with ESMTP id l68DoHBr020595
for <gentoo-dev@lists.gentoo.org>; Sun, 8 Jul 2007 13:50:18 GMT
Received: by ug-out-1314.google.com with SMTP id a2so1079392ugf
for <gentoo-dev@lists.gentoo.org>; Sun, 08 Jul 2007 06:50:18 -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=T9YrjVdY8AI86YJwCjkMLm2d46jz26MvN5HB3juymcOCcU9qDT+E/N8NA0sHKvv3g3rej2w4zHct43PHalvpvqoZDFWPYMMqlp8zACwX/q4qRoF3y/fvB1cB75OajadvN2/Ga2paUvaRigUpBsFCEfFnyfSl9Heh1TKin4TuQWY=
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=Cn8BMM6UVAarTgWX9pk6rYQmFStfN/Fz9gLd+gxirwjnYobDWX9QL53kM5lXY4z/0Y9vapRVr78QCToB++WaqkRsN+McAj0HazwiGU64r3I4YCy19bvu5QiPWzIvlDaTIEadJPjkgNPBg8K86ufGThQkJEOYKp4BVz591/QMcyc=
Received: by 10.78.171.20 with SMTP id t20mr1090515hue.1183902617321;
Sun, 08 Jul 2007 06:50:17 -0700 (PDT)
Received: by 10.78.46.12 with HTTP; Sun, 8 Jul 2007 06:50:17 -0700 (PDT)
Message-ID: <2bd962720707080650j449b85e7rad987d6b14925f47@mail.gmail.com>
Date: Sun, 8 Jul 2007 09:50:17 -0400
From: "Ryan Reich" <ryan.reich@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Inotify and (f)crontabs
In-Reply-To: <200707080022.49121.vapier@gentoo.org>
Precedence: bulk
List-Post: <mailto:gentoo-dev@lists.gentoo.org>
List-Help: <mailto:gentoo-dev+help@gentoo.org>
List-Unsubscribe: <mailto:gentoo-dev+unsubscribe@gentoo.org>
List-Subscribe: <mailto:gentoo-dev+subscribe@gentoo.org>
List-Id: Gentoo Linux mail <gentoo-dev.gentoo.org>
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>
<200707072321.28435.vapier@gentoo.org>
<2bd962720707072107w5f9594cdl6d6183262ed103df@mail.gmail.com>
<200707080022.49121.vapier@gentoo.org>
X-Archives-Salt: 94274b72-0055-4576-bcf3-58d35059cab2
X-Archives-Hash: 3c809dac4325fee18d483dadfa1ee604
On 7/8/07, Mike Frysinger <vapier@gentoo.org> wrote:
> On Sunday 08 July 2007, Ryan Reich wrote:
> > 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?
>
> run-crons transparently gives all crons this behavior with very little
> overhead rather than making every user set up a dual system: a standard cron
> and anacron.
>
> run-crons is a default helper for crons that just works. if you want to not
> use it but opt for anacron instead, nothing is stopping you from doing
> exactly that.
What is the additional overhead of using cron+anacron as compared to
using cron+run-crons? The README in anacron's tarball indicates that
the net difference is one bootscript. Otherwise, you (by which I mean
"the developers" as opposed to "the person using anacron") just take
most of the existing /etc/crontab and put it (or its anacron
equivalent) in /etc/anacrontab, and with the rest you have cron run
anacron once a night. The user wouldn't have to do any more setup
than currently; it would just work.
--
Ryan Reich
--
gentoo-dev@gentoo.org mailing list