On 2026-04-13 15:53:23 +0200, Fiona Klute wrote: > Am 13.04.26 um 15:29 schrieb Lin Qigang: > > So anacron 2.3-49 is now in experimental for testing that Type=oneshot > > is the issue. After some testing this is the issue, I will upload > > anacron 2.3-50 to unstable and close this bug. Thank you again for > > testing! > This makes sense: If Type is unset systemd assumes "simple", which considers > the service up as soon as the process has been forked off, while "oneshot" > waits for it to exit.
This is also what I understand from the systemd.service(5) man page. > But why is anacron.service started during installation at all? Shouldn't > only the timer unit be started, which can then start the service unit in > turn if needed (in the background)? I'm wondering the same thing. The cron jobs would have probably been run already (without anacron installed). This would mean that the jobs would be run again, and this seems incorrect (not tested). > If my understanding is correct and the service unit should be started only > via the timer, the actual problem is likely the [Install] section (which > makes the service run independently of the timer). None of the other service > units started via timer on my system have it. I agree that this would make more sense. -- Vincent Lefèvre <[email protected]> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / Pascaline project (LIP, ENS-Lyon)
