reported timestamps during boot process?
smithi at nimnet.asn.au
Sat Mar 12 14:01:49 UTC 2016
In freebsd-questions Digest, Vol 614, Issue 7, Message: 17
On Sat, 12 Mar 2016 09:18:35 +0100 From: Michael Grimm <trashcan at ellael.org> wrote:
> Erich Dollansky <erichsfreebsdlist at alogt.com> wrote:
> > Michael Grimm <trashcan at ellael.org> wrote:
> >> Is there a way to investigate the boot process by means of reported
> >> timestamps in some logfile? dmesg doesn't seem to be the tool of
> >> choice.
> > you might find some hints in /var/log/messages.
> Nope. It looks to me  that, whilst booting, kernel messages are
> written to that file in one batch after syslogd has been fired up.
> Timestamps of those messages are all showing the very same second.
>  is that correct?
That's correct, everything is buffered in memory before that. 'rcorder
/etc/rc.d/*' shows syslogd being started after lots of other services,
after FILESYSTEMS are up and, in case of remote logging, NETWORKING.
> Linux' dmesg has such a feature  I am looking for:
> | -d, --show-delta
> | Display the timestamp and the time delta spent between
> | messages. If used together with ?notimee then only the time
> | delta without the timestamp is printed.
>  http://man7.org/linux/man-pages/man1/dmesg.1.html
You could call that feature-rich or bloated, depending on inclination :)
I rather doubt that would apply to boot messages anyway. Looking at the
boot messages (here kern.log.0) on an admittedly much older Linux 2.6.18
system, all 236 lines have just the same timestamp, just as on FreeBSD,
but of course you could test that on some Linux system's boot messages.
I don't know whether message storage has any internal microtime stamp
you could use for this, but suspect that would take quite some kernel
hackery, before userland patches to view them. Maybe ask on hackers@ ?
More information about the freebsd-questions