We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Forwarded from https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829438 .
I have seen the same behaviour, but I have no clue.
Systemd service cron-daily.service has line
ExecStartPre=/lib/systemd-cron/boot_delay 5
which makes it wait until system's uptime is at least 5 minutes. The delay is also part of Systemd's startup time as reported by journal:
[...] systemd[1]: Startup finished in 4.159s (kernel) + 4min 58.016s (userspace) = 5min 2.175s.
See the userspace and total time. The delay also shows in the graph produced by command "systemd-analyze plot" (I'll try to include an attachment).
This is a minor issue but it would be nice if cron services weren't part of the startup time.
Teemu Likonen
The text was updated successfully, but these errors were encountered:
systemd-analyze critical-chain can be usefull to debug
systemd-analyze critical-chain
Sorry, something went wrong.
https://www.linux-magazine.com/Issues/2018/212/The-sys-admin-s-daily-grind-systemd-analyze
No branches or pull requests
Forwarded from https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829438 .
I have seen the same behaviour, but I have no clue.
Systemd service cron-daily.service has line
which makes it wait until system's uptime is at least 5 minutes. The
delay is also part of Systemd's startup time as reported by journal:
See the userspace and total time. The delay also shows in the graph
produced by command "systemd-analyze plot" (I'll try to include an
attachment).
This is a minor issue but it would be nice if cron services weren't part
of the startup time.
Teemu Likonen
The text was updated successfully, but these errors were encountered: