Control: tags -1 + moreinfo
On Fri, 30 Apr 2021 10:46:04 -0700 Ross Boylan wrote: [...] > Dear Maintainer, Hello Ross, thanks for your bug report. > > It would be nice to clean up this minor annoyance before buster's release. I am afraid that we are too late for *buster* release. Maybe you meant *bullseye*?!? ;-) Anyway, it's late for bullseye, as well: Debian testing is already in hard freeze... But I don't think there's anything really in need for a fix. Please read on. > > * What led up to the situation? > > Installed apt-listbugs and logcheck on a debian testing system. > Every *hour* I get email from logcheck that includes lines like this: > Apr 30 08:37:06 debtest systemd[1]: Starting Daily apt-listbugs > preferences cleanup... > Apr 30 08:37:06 debtest systemd[1]: Finished Daily apt-listbugs > preferences cleanup. > (Obviously logcheck and the email are incidental; the point is the > "Daily" cleanup is actually run hourly. However, the emails are > part of why I find it annoying.) 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 > > * What exactly did you do (or not do) that was effective (or > ineffective)? > > Investigated why this is happening. The package has an entry in > /etc/cron.daily, which seems correct. But it also has > /lib/systemd/system/apt-listbugs.timer which includes > OnCalendar=*-*-* *:20 > I believe this is telling it to trigger something at 20 minutes > after the hour for every hour. There is also > RandomizedDelaySec=20min > in the same file, which may explain why it seems to run between 20 > and 40 minutes after the hour for me. Yes, that is correct. Please read bug [#932995] for a more detailed discussion about the same surprise you experienced. [#932995]: <https://bugs.debian.org/932995> > > This seems more like a task for anacron for systems that may not be > up all the time, but I don't know enough about systemd to be sure > how to turn it off, or if it can handle these situations. If you use systemd as your init system (PID 1), please do not turn it off. It's the only apt-listbugs cleanup routine running, since the cron.daily job does nothing, if systemd is PID 1. > > * What was the outcome of this action? > Only observations so far, and so no change. I might change to > OnCalendar=*-*-* 20:20 > which I think means run at 8:20pm every day. But the VM is not up > all the time and so that might miss some times it should run, > unless the /etc/cron.daily/ entry acts as a safety net. That is exactly the reason why the cleanup is attempted hourly, but performed at most once a day. Again, see [#932995] for an explanation. > > * What outcome did you expect instead? > That a daily cleanup job would only run once a day. That's already happening: the cleanup runs at most once a day. > > 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. I am not knowledgeable enough about logcheck to help you in this. Sorry about that. > > Thanks for your work on the package:) You're welcome, I try to do my best... If you do not object, I will close this bug report. -- 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
pgpbMqLTlSKbo.pgp
Description: PGP signature
