1 |
Am Mon, Dec 13, 2021 at 03:18:44PM -0500 schrieb Rich Freeman: |
2 |
> On Sun, Dec 12, 2021 at 2:07 PM Frank Steinmetzger <Warp_7@×××.de> wrote: |
3 |
> > |
4 |
> > Am Sun, Dec 12, 2021 at 01:41:33PM -0500 schrieb Rich Freeman: |
5 |
> > > On Sun, Dec 12, 2021 at 1:21 PM Frank Steinmetzger <Warp_7@×××.de> wrote: |
6 |
> > > > |
7 |
> > > |
8 |
> > > I don't use this, but I believe there should be an hourly crontab |
9 |
> > > entry that deletes the cron.hourly file, which would mean it gets run |
10 |
> > > on the next 10min cycle (or maybe sooner - I'm not sure if those jobs |
11 |
> > > are run in parallel or serial). |
12 |
> > |
13 |
> > The check that I mentioned above is actually the deletion which you mention: |
14 |
> > run-crons looks for the state file for the given interval and - if it is old |
15 |
> > enough - deletes it. |
16 |
> |
17 |
> The check I'm talking about isn't in run-crons at all. It is in |
18 |
> /etc/crontab. It doesn't look at the age of the file and |
19 |
> unconditionally deletes it every hour: |
20 |
> 59 * * * * rm -f /var/spool/cron/lastrun/cron.hourly |
21 |
|
22 |
I had a look at files and docs on the net again. Thus I found exactly those |
23 |
rm entries in /etc/crontab, which by itself is not used by fcron. But after |
24 |
I understood all the logic behind it, I added them to fcron to be run |
25 |
serially before run-crons. Now everything is as I wanted it. |
26 |
|
27 |
For the record: The checks in run-crons that I referred to earlier are |
28 |
actually more for those cases in which the machine was powered off for a |
29 |
while in order to restore cron completeness as early as possible after boot. |
30 |
|
31 |
-- |
32 |
Grüße | Greetings | Qapla’ |
33 |
Please do not share anything from, with or about me on any social network. |
34 |
|
35 |
“Selfies are electronic masturbation.” — Karl Lagerfeld |