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

systemd-analyze: Please show initrd time for initrds that do not use systemd #32726

Open
bdrung opened this issue May 8, 2024 · 1 comment
Open
Labels
analyze needs-discussion 🤔 RFE 🎁 Request for Enhancement, i.e. a feature request

Comments

@bdrung
Copy link
Contributor

bdrung commented May 8, 2024

Component

systemd-analyze

Is your feature request related to a problem? Please describe

systemd-analyze shows the time spent in the initrd in case systemd is used in the initrd. It does not show the time spent in the initrd if systemd is not used inside (e.g. when using initramfs-tools).

Describe the solution you'd like

I like to change initramfs-tools to report the needed timestamp so that systemd-analyze can report/calculate the time spent in the initrd. I haven't found documentation about it. The simplest solution would probably to store /proc/uptime somewhere in /run at the beginning of the initrd.

Describe alternatives you've considered

No response

The systemd version you checked that didn't have the feature you are asking for

255

@bdrung bdrung added the RFE 🎁 Request for Enhancement, i.e. a feature request label May 8, 2024
@poettering
Copy link
Member

frankly, an initrd without systemd is a really weird idea that might work in corner cases where you know your hw and used storage and stuff, but is really weird for the generic case. While we shouldn't explicitly break that of course I am not convinced we really should add more integration hooks for that, it's a flawed model. Any non-trivial setup will need a service manager in the initrd anyway...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
analyze needs-discussion 🤔 RFE 🎁 Request for Enhancement, i.e. a feature request
Development

No branches or pull requests

2 participants