On Sun 03 Mar 2024 at 13:27:50 (+0100), Eduard Bloch wrote: > * David Wright [Sun, Feb 11 2024, 10:20:16PM]: > > On Sun 11 Feb 2024 at 20:41:51 (+0000), Darac Marjal wrote: > > > On 11/02/2024 11:21, Rainer Dorsch wrote: > > > > > > - How do I set a timeout/limit for anacron, that it cannot block forever > > > > during a reboot? > > > > > > It may be germane to point out that anacron.service already explicitly > > > sets "TimeoutStopSec=Infinity". So, in the opinion of the developers, > > > the service shouldn't be prematurely killed. Of course you, as the > > > system administrator, always have the right to countermand that sort > > > of decision, but it would be curious to find out why the developers > > > thought they needed to override the systemd default in the first > > > place? > > > > Bug #915379 explains all: long-running cron jobs, like backups, can > > get killed, and there was also an issue with exim. > > Yes, and?
If you don't like it, then # systemctl edit --full anacron.service and remove or decrease the timeout, which means (for removal) you'll be reverting to how things are in bullseye. > The opposite is: you have some stupid (and UNKNOWN) task which > hangs forever because of some programming bug. And then your whole system > locks up, unable to reboot, and no way to recover it because the reboot > is stuck because of this. I am observing this on my old hacking laptop > right now, the system took many minutes (5? 7?) to continue, but even > that was pure luck. I would probably have force-powered-down by then. > Sorry, no, that cannot be the proper way. I am reopening 915379 now, the > maintainer should maybe come up with some sane solution. #915379 has been archived, which AIUI means you need to open a new one. Cheers, David.