Hello Lance, thanks for your analysis. On Fri, Sep 30, 2022 at 12:53:09PM +0000, Lance Lin wrote: > Thank you for your help in tracking this down. I apologize that the -35 > revision didn't fix it. > > > So the check in the cron file is wrong! It should be > > if [ -d /run/systemd/system ]; then … > > > > > Is this the solution? Or is there a downside in changing this? And I > > definitely did not configure this manually. And if I log at old log > > entries (when anacron was still working fine), the call is the same: > > Jul 16 20:30:01 twentytwo CRON[15482]: (root) CMD ([ -x /etc/init.d/anacron > > ] && if [ ! -d /run/systemd/system ]; then /usr/sbin/invoke-rc.d anacron > > start >/dev/null; fi) > > It could be. I have not changed d/cron.d at all. The only changes I made were > to the service file (d/anacron.service) and that > > was after input from another user saying the timeout > (TimeoutStopSec=infinity). Perhaps this caused the problem? Maybe this is > something > we could both test (e.g. deleting this line)? The user said the change was > just strictly better and suited their needs as well as the typical > functionality. > See Bug#915379.
I just deleted this line in /usr/lib/systemd/system/anacron.service
and then run
systemctl restart anacron
(Hope this is right)
> If anacron was working before, this is now the only change since -32. If this
> breaks anacron, I am happy to remove the TimeoutStopSec line.
I'll report the outcome.
Greetings
Helge
P.S. Is there some explanation about the check of
"! -d /run/systemd/system"
?
--
Dr. Helge Kreutzmann deb...@helgefjell.de
Dipl.-Phys. http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
Help keep free software "libre": http://www.ffii.de/
signature.asc
Description: PGP signature
