Skip to content
New issue

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

cron-{daily, weekly, monthly}.service (and boot_delay) is part of the system's startup time #50

Open
a-detiste opened this issue Jan 10, 2017 · 2 comments
Labels
bug-in-systemd Bug in systemd itself

Comments

@a-detiste
Copy link
Contributor

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

@a-detiste a-detiste added the bug-in-systemd Bug in systemd itself label Aug 12, 2023
@a-detiste
Copy link
Contributor Author

systemd-analyze critical-chain can be usefull to debug

@a-detiste
Copy link
Contributor Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug-in-systemd Bug in systemd itself
Projects
None yet
Development

No branches or pull requests

1 participant