On Sat, 1 May 2021 11:31:19 -0700 Ross Boylan wrote: [...] > On Fri, Apr 30, 2021 at 2:47 PM Francesco Poli > <invernom...@paranoici.org> wrote: [...] > > Does logcheck send e-mail messages for all the other systemd timers? > > > > As you may already know, you can get a list of active systemd timers on > > your box with the following command: > > > > $ systemctl list-timers > > > Thanks for the tip; I wasn't familiar with list-timers. There are 11 > on my list, but the only things I see in my hourly reports from > logcheck were apt-listbugs and complaints about time synchronization.
Do you have anacron installed? It's another package that has an hourly systemd timer. I wonder why logcheck does not send hourly mail messages about anacron... > Of course, I don't know how many of the timers are hourly. The command 'systemctl list-timers' should tell you: just look at the LEFT and PASSED columns. Or you could read the timer definitions, if you know (or learn) the syntax and semantics... [...] > I tried this modification to apt-listbugs.timer: > [Timer] > OnActiveSec=5min > #OnCalendar=*-*-* *:20 > OnUnitActiveSec=23h 50m > RandomizedDelaySec=20min > > which did fix the "running every hour" problem (even if the run is > only to check if a real update is necessary). > But this does not entirely meet the desired behavior expressed in 932995: [...] Not only that, but there's also another issue with this modification. The timer would only trigger once every (slightly less than one) day: if your system is not online during that only attempt, you are out of luck for another day or so... > > > > > > Another work-around for the visible annoyance would be for me to tell > > > logcheck to ignore the relevant messages. > > > > I think this should be the way to avoid the annoyance. > > It avoids the annoyance of seeing the message, but it leaves the job > firing every hour. I think this is needed to have some reasonable chance to get one successful cleanup operation a day. [...] > > If you do not object, I will close this bug report. > > > I suppose, though, as observed in the other bug you mentioned, the > message about "daily update" is confusing. The fact that other > packages aren't exhibiting such behavior suggests there is some other > way to handle this, but I certainly don't know what it is. I am open to suggestions on how to change the Description field for the timer. I see that the Description for the anacron timer is "Trigger anacron every hour": maybe I should think about a Description that uses the word "hourly", rather than "daily". But then I am afraid I would get bug reports from people saying that an hourly cleanup is too frequent and asking to reduce the frequency to daily! I think that applying the principle of least surprise is especially tricky in this case... -- http://www.inventati.org/frx/ There's not a second to spare! To the laboratory! ..................................................... Francesco Poli . GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE
pgpCBPJIoZoVX.pgp
Description: PGP signature
