On Thu, 27 Apr 2023, 20:57 richardn, <richard...@gmail.com> wrote: Thanks for the bug report - this is an interesting one! (see below)
/lib/systemd/system/chkrootkit.timer contains - > > # then run every day > OnUnitActiveSec=24h > > This is a monotonic timer. According to systemd.timer manpage - > > These are monotonic timers, independent of wall-clock time and > timezones. If the computer is temporarily suspended, the monotonic > clock generally pauses, too. > a realtime (i.e. wallclock) timer should be used e.g > > OnCalendar=daily > maybe, although also - if the system is suspended for 24h, is there actually a benefit in having the check run on resume? as you say, it will (i think - it seems to work for me!) run once the system has been active for a cumulative 24h you can do 'systemctl edit systemd.timer' and make a drop-in that changes the setting locally (you might need to reset OnUnitActiveSec to empty as well as setting OnCalendar=daily in the drop-in file) i'm not sure what the debian policy on this is (i dont think there is one?), or what the best default is - am not at all averse to changing the default, but given: - how close to the bookworm release we are - this seems to be a matter of opinion as to what setting is the best default - it's quite hard to properly test the impact of these settings - how easy it is to change locally (see above) i am tempted to leave it as-is for now (and revisit post-release) - if other people think the default should change, please respond to this bug too!
