From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gentoo-user+bounces-197601-garchives=archives.gentoo.org@lists.gentoo.org>
Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
	 key-exchange X25519 server-signature RSA-PSS (2048 bits))
	(No client certificate requested)
	by finch.gentoo.org (Postfix) with ESMTPS id 6C65C158086
	for <garchives@archives.gentoo.org>; Mon, 13 Dec 2021 21:42:35 +0000 (UTC)
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
	by pigeon.gentoo.org (Postfix) with SMTP id 799912BC049;
	Mon, 13 Dec 2021 21:42:29 +0000 (UTC)
Received: from smtp.gentoo.org (mail.gentoo.org [IPv6:2001:470:ea4a:1:5054:ff:fec7:86e4])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
	 key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256)
	(No client certificate requested)
	by pigeon.gentoo.org (Postfix) with ESMTPS id 5E4572BC020
	for <gentoo-user@lists.gentoo.org>; Mon, 13 Dec 2021 21:42:28 +0000 (UTC)
Message-ID: <1e7ebc2410db0e42c7692f951c6614061d0004bb.camel@gentoo.org>
Subject: Re: [gentoo-user] Bug in run-crons?
From: Michael Orlitzky <mjo@gentoo.org>
To: gentoo-user@lists.gentoo.org
Date: Mon, 13 Dec 2021 16:42:24 -0500
In-Reply-To: <Ybe9Ov1vtxXWZCRo@kern>
References: <YbY9p57DJZhobltL@kern>
	 <CAGfcS_==3kkTFRVG1=01z7vP7rfuSca_nyNJ8WpW8tDz_zM7GA@mail.gmail.com>
	 <YbZIhcaZCHqjPCbN@kern>
	 <CAGfcS_kb--bq01Qxmq4Mx7AqFs36Pag1zjhkEGAyhfuyhiVp-g@mail.gmail.com>
	 <Ybe4yYan1Oe4YxMx@kern>
	 <0fa56046dbf46a92723f588f2b458deb53771c5c.camel@gentoo.org>
	 <Ybe9Ov1vtxXWZCRo@kern>
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.40.4 
Precedence: bulk
List-Post: <mailto:gentoo-user@lists.gentoo.org>
List-Help: <mailto:gentoo-user+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-user+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-user+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-user.gentoo.org>
X-BeenThere: gentoo-user@lists.gentoo.org
Reply-to: gentoo-user@lists.gentoo.org
X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
X-Archives-Salt: 54eb501a-4c7e-4e50-bec2-217ee61aea47
X-Archives-Hash: c0c3064939f43579b81a95289064f8a9

On Mon, 2021-12-13 at 22:38 +0100, Frank Steinmetzger wrote:
> 
> Well I *could* disable run-crons altogether and add entries to fcron’s own
> crontab which would run those scripts in /etc/cron.{hourly,daily,...}
> instead.
> 
> However, I like predictable times at which those jobs will run. Especially
> if one of them is a zfs scrub; the NAS is powered down for weeks, sometimes
> months. And when I power it up, it’s for a reason. And that reason usually
> is not a scrub, which—at the current zfs fill level—takes 10½ hours.
> 

Why choose fcron then? It sounds like you have the same rationale as I
do: "no, I don't want to run the 4am backup job in the middle of the
business day just because it wasn't run at 4am."

If you pick a dumber cron, the crontab entries are run only at the
specified times.