Boucman
d21b0c826f
the whole systemd-analyze time logic is based on the fact that monotonic time 0 is the start of the kernel. If the firmware does not provide a correct time, firmware_time degrades to 0, which is the start of the kernel. The diference between FinishTime and firmware_time is thus correct. That assumption is still true with containers, but the start time of the kernel is not what the user expects : It's the time when the host booted. The total is thus still correct, but highly misleading. Containers can be easily detected (and, in fact, already are) by systemd not reporting any kernel non-monotonic timestamp. This patch simply avoids printing a misleading time when it can detect that case
systemd - System and Service Manager
Details
General information about systemd can be found in the systemd Wiki.
Information about build requirements are provided in the README file.
Consult our NEWS file for information about what's new in the most recent systemd versions.
Please see the HACKING file for information how to hack on systemd and test your modifications.
Please see our Contribution Guidelines for more information about filing GitHub Issues and posting GitHub Pull Requests.
When preparing patches for systemd, please follow our Coding Style Guidelines.
If you are looking for support, please contact our mailing list or join our IRC channel.