From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gentoo-user+bounces-197598-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 0A6D5158086
	for <garchives@archives.gentoo.org>; Mon, 13 Dec 2021 21:33:42 +0000 (UTC)
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
	by pigeon.gentoo.org (Postfix) with SMTP id 0BC6E2BC027;
	Mon, 13 Dec 2021 21:33:36 +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 83746E0848
	for <gentoo-user@lists.gentoo.org>; Mon, 13 Dec 2021 21:33:35 +0000 (UTC)
Message-ID: <0fa56046dbf46a92723f588f2b458deb53771c5c.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:33:32 -0500
In-Reply-To: <Ybe4yYan1Oe4YxMx@kern>
References: <YbY9p57DJZhobltL@kern>
	 <CAGfcS_==3kkTFRVG1=01z7vP7rfuSca_nyNJ8WpW8tDz_zM7GA@mail.gmail.com>
	 <YbZIhcaZCHqjPCbN@kern>
	 <CAGfcS_kb--bq01Qxmq4Mx7AqFs36Pag1zjhkEGAyhfuyhiVp-g@mail.gmail.com>
	 <Ybe4yYan1Oe4YxMx@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: 7bit
X-Archives-Salt: b8583886-9c21-48f9-9613-f3a357e82415
X-Archives-Hash: fe2a6f9db1d120ff57c96746a830565a

On Mon, 2021-12-13 at 22:19 +0100, Frank Steinmetzger wrote:
> 
> For the record: The checks in run-crons that I referred to earlier are
> actually more for those cases in which the machine was powered off for a
> while in order to restore cron completeness as early as possible after boot.
> 

The run-crons quackery has been causing problems since 2004:

  https://bugs.gentoo.org/69777

One-liners with run-parts (NOT run-crons) are a lot more predictable.