-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 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.
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. cer@Telcontar:~> grep "Starting Do daily mandb update\|Finished Do daily mandb update" /var/log/messages <3.6> 2023-02-24T00:00:02.256852+01:00 Telcontar systemd 1 - - Finished Do daily mandb update. <3.6> 2023-02-25T00:00:01.561800+01:00 Telcontar systemd 1 - - Starting Do daily mandb update... <3.6> 2023-02-25T00:00:03.518819+01:00 Telcontar systemd 1 - - Finished Do daily mandb update. <3.6> 2023-02-26T00:00:01.766809+01:00 Telcontar systemd 1 - - Starting Do daily mandb update... <3.6> 2023-02-26T00:00:03.002047+01:00 Telcontar systemd 1 - - Finished Do daily mandb update. cer@Telcontar:~> 2". It is an M2 disk. cer@Telcontar:~> grep "Starting Rotate log files\|Finished Rotate log files" /var/log/messages <3.6> 2023-02-24T00:00:02.272908+01:00 Telcontar systemd 1 - - Finished Rotate log files. <3.6> 2023-02-25T00:00:01.563275+01:00 Telcontar systemd 1 - - Starting Rotate log files... <3.6> 2023-02-25T00:00:03.519266+01:00 Telcontar systemd 1 - - Finished Rotate log files. <3.6> 2023-02-26T00:00:01.768163+01:00 Telcontar systemd 1 - - Starting Rotate log files... <3.6> 2023-02-26T00:00:03.940346+01:00 Telcontar systemd 1 - - Finished Rotate log files. cer@Telcontar:~> 2". It is an M2 disk. cer@Telcontar:~> grep "Starting Update locate database...\|Finished Update locate database." /var/log/messages <3.6> 2023-02-24T00:00:03.318721+01:00 Telcontar systemd 1 - - Finished Update locate database. <3.6> 2023-02-25T00:00:01.564561+01:00 Telcontar systemd 1 - - Starting Update locate database... <3.6> 2023-02-25T00:00:29.706891+01:00 Telcontar systemd 1 - - Finished Update locate database. <3.6> 2023-02-26T00:00:01.769485+01:00 Telcontar systemd 1 - - Starting Update locate database... <3.6> 2023-02-26T00:00:59.713500+01:00 Telcontar systemd 1 - - Finished Update locate database. cer@Telcontar:~> Almost one minute, depends on the day. There are 4 rotating rust disks to explore. - -- Cheers, Carlos E. R. (from openSUSE 15.4 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCY/uaYBwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfV5Y0AnjV1WLIx2ilVr3V9+Hg4 Qb9eTYyPAJ9096yxzPaOUzFYShay2dbQLr/Oug== =jKvi -----END PGP SIGNATURE-----