[systemd-devel] Plot time data anomalies
Lennart Poettering
lennart at poettering.net
Mon Jan 16 12:37:17 UTC 2023
On Mi, 11.01.23 15:13, Joshua Zivkovic (joshua.zivkovic at codethink.co.uk) wrote:
> > > Also note that services that are not referenced by anything (and
> > > didn't fail) might have been unloaded (i.e. "GC'ed"), which means
> > > their startup timing info is released and won't show up in the
> > > displayed data either.
> >
> > I added some explanatory docs for this now, in this PR:
> >
> > https://github.com/systemd/systemd/pull/26019
> >
> As a comment points out, what happens if a unit gets stopped and
> started during boot? This is what I noticed in the time data, some
> units are being stopped and started again during boot, not
> afterwards.
We only store the timestamps of one invocation in PID 1 of each
service. And that's the most recent one. If you start it 27 times in a
row, then the 26 first ones are flushed out, and we only show the 27th one.
Lennart
--
Lennart Poettering, Berlin
More information about the systemd-devel
mailing list