Am Mon, Dec 13, 2021 at 03:18:44PM -0500 schrieb Rich Freeman:
> On Sun, Dec 12, 2021 at 2:07 PM Frank Steinmetzger <Warp_7@gmx.de> 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 <Warp_7@gmx.de> 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

I had a look at files and docs on the net again. Thus I found exactly those
rm entries in /etc/crontab, which by itself is not used by fcron. But after
I understood all the logic behind it, I added them to fcron to be run
serially before run-crons. Now everything is as I wanted it.

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.

-- 
Grüße | Greetings | Qapla’
Please do not share anything from, with or about me on any social network.

“Selfies are electronic masturbation.” — Karl Lagerfeld