On 2023-02-26 19:18, Dave Howorth wrote:
On Sun, 26 Feb 2023 18:44:00 +0100 (CET) "Carlos E. R." <> wrote: >> El 2023-02-26 a las 13:36 -0000, Dave Howorth escribió:
On Sun, 26 Feb 2023 12:46:42 +0100 "Carlos E. R." <> wrote:
On 2023-02-26 12:22, Dave Howorth wrote:
On Sun, 26 Feb 2023 09:25:26 +0100 "Carlos E. R." <> wrote:
On 2023-02-26 07:04, Felix Miata wrote: > # journalctl -b --no-hostname| grep "Feb 25" | egrep -v > 'smartd|rpc' Feb 25 00:00:47 systemd[1]: Starting Do daily mandb > update... Feb 25 00:00:47 systemd[1]: Starting Rotate log > files... Feb 25 00:00:47 systemd[1]: Starting Update locate > database... Feb 25 00:00:47 systemd[1]: logrotate.service: > Deactivated successfully. Feb 25 00:00:47 systemd[1]: Finished > Rotate log files. Feb 25 00:00:47 systemd[1]: mandb.service: > Deactivated successfully. Feb 25 00:00:47 systemd[1]: Finished > Do daily mandb update.
What is mystifiying to me is that the three tasks start simultaneously, and the three end in zero seconds.
Well if multiple services are started at the same time and are short-running it must be more likely than not, surely? If you had timestamps to milliseconds or more precisely then you might see a difference.
But I would expect to see:
Starting Do daily mandb update... Finished Do daily mandb update. Starting Rotate log files... Finished Rotate log files. Starting Update locate database... Finished Update locate database.
Why, if the jobs are started in parallel?
That's the problem, they shouldn't. Before systemd, they happened in sequence.
Err, you're complaining because systemd improved things and runs jobs in parallel!!? It's called progress, not problem.
It is not progress nor improvement. When that thing triggers I have to stop using the machine and wait till it finishes, or the brunt of it finishes. Hard disk can hardly parallelize, it is sequential in essence. It is not CPU intensive, it is hard disk intensive.
The three jobs are demanding on the hard disk.
Apparently not particularly except for the locate databse task.
On my computer, they are very demanding. Specially if the machine is rotating rust. There have been times when these jobs started that the machine became unresponsive for a while.
OK, but you were not commenting about your computer and we're not discussing that. You were commenting about Felix's situation. I didn't claim the condition would always be true on all machines!
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. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)