From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: 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 7EF51158086 for ; Mon, 13 Dec 2021 20:19:12 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 389EF2BC020; Mon, 13 Dec 2021 20:19:02 +0000 (UTC) Received: from mail-oi1-f173.google.com (mail-oi1-f173.google.com [209.85.167.173]) (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 9E834E041F for ; Mon, 13 Dec 2021 20:18:57 +0000 (UTC) Received: by mail-oi1-f173.google.com with SMTP id t23so24723763oiw.3 for ; Mon, 13 Dec 2021 12:18:57 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=nyaqAPwspCECqkIafrOpfSihfvvjvksnFEUuyX7HPTA=; b=qpjRLnMkX6zKAvaGM+U1lPhuuJoe4ZTMiXb68T7PM1tPI4xCizBwnS9K1o0hu9cdIu afS5TYobfXxOhQbmVT6aki+koC11MnOFK1B5FKbYuI95jBAhkXCZeWQgCxRX5cJr8q6z 0dZ6NEcmC0DMNZ5kUFXZy7iOvCQ6SMPgmVTMaO/J5pg+x6FbTnVAkn4NzFoYKeFx2I16 l7Ge+2R4gVGKZ1Qcjq9P+ynamZ6by6YerHcoJxajohxtaUdR5cBQjuioTAGXedTItULd uFWnW0q8gUG9rsQMewB3p2v+92088ESMXt6N98wiml5tkGbP/UANxRH2nYfQ9bOjcmun bY1w== X-Gm-Message-State: AOAM530orqn++VzKvkqUIAH5VjeFC7RfWeV5w2N3ToHqxkF8/SkWWPka AbBZ0yhYKzYS8Pd5D1xMKtnxDMgf+SkMMhw5wt7IwOz8DQE= X-Google-Smtp-Source: ABdhPJzVmT8DC8098pSG23mNzwZlIB0/VYC/jY+Q+fkHqsWPmranKCRjAFVC5yMLd5z57HHwbwmMp+fPrFHDdn/izuQ= X-Received: by 2002:aca:eb53:: with SMTP id j80mr708117oih.85.1639426735162; Mon, 13 Dec 2021 12:18:55 -0800 (PST) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail 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 References: In-Reply-To: From: Rich Freeman Date: Mon, 13 Dec 2021 15:18:44 -0500 Message-ID: Subject: Re: [gentoo-user] Bug in run-crons? To: gentoo-user@lists.gentoo.org Content-Type: text/plain; charset="UTF-8" X-Archives-Salt: 5338b69e-a7f1-433c-af0d-ffe35ea2badb X-Archives-Hash: 5dba85bb39b5e9730eed3b9cba57a88d On Sun, Dec 12, 2021 at 2:07 PM Frank Steinmetzger wrote: > > Am Sun, Dec 12, 2021 at 01:41:33PM -0500 schrieb Rich Freeman: > > On Sun, Dec 12, 2021 at 1:21 PM Frank Steinmetzger wrote: > > > > > > > I don't use this, but I believe there should be an hourly crontab > > entry that deletes the cron.hourly file, which would mean it gets run > > on the next 10min cycle (or maybe sooner - I'm not sure if those jobs > > are run in parallel or serial). > > The check that I mentioned above is actually the deletion which you mention: > run-crons looks for the state file for the given interval and - if it is old > enough - deletes it. The check I'm talking about isn't in run-crons at all. It is in /etc/crontab. It doesn't look at the age of the file and unconditionally deletes it every hour: 59 * * * * rm -f /var/spool/cron/lastrun/cron.hourly -- Rich