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 |
||
---|---|---|
.. | ||
analyze-verify.c | ||
analyze-verify.h | ||
analyze.c | ||
meson.build |