On Sun, 26 Feb 2023, 22:58:56 +0100, Carlos E. R. wrote:
On 2023-02-26 20:44, Manfred Hollstein wrote:
On Sun, 26 Feb 2023, 20:03:44 +0100, Carlos E. R. wrote:
On 2023-02-26 19:46, Felix Miata wrote:
Carlos E. R. composed on 2023-02-26 19:27 (UTC+0100):
I simply noticed the situation in Felix output, then came to realize that my machine does the same, and that is why it was so severely impacted when the daily jobs trigger.
So customize! Don't fire multiple timed tasks at the same time. Move the times to when you're normally not awake.
That's what I am thinking to do, but I do not know how they are fired. Have not started the investigation.
Oh, wait, move to when I am not awake, you say. No, that does not happen, I hibernate the machine when I go to sleep.
Carlos, we had a long discussion about this when systemd timers should take over the behaviour of cron to run 15 minutes after starting/resuming. The result of that was to install cronie-anacron to enable a similar behaviour. Systemd timers are not usable for machines not running 24 hrs a day.
If I have to go that way, I would simply restore from backup the old suse cron scripts.
My machine is certainly not running 24/7, yet the jobs are running. Somewhere they must be configured.
Sure, it's all documented in systemd.timer(5). Cheers. l8er manfred