Date: Fri, 14 Oct 2011 09:36:13 +0000 From: Alexander Best <arundel@freebsd.org> To: Poul-Henning Kamp <phk@phk.freebsd.dk> Cc: Nikolay Denev <ndenev@gmail.com>, FreeBSD Current <freebsd-current@freebsd.org>, Arnaud Lacombe <lacombar@gmail.com> Subject: Re: [RFC] Prepend timestamp in msgbuf Message-ID: <20111014093613.GA15025@freebsd.org> In-Reply-To: <20111014092445.GA11785@freebsd.org> References: <20111014085609.GA3799@freebsd.org> <40448.1318582809@critter.freebsd.dk> <20111014092445.GA11785@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri Oct 14 11, Alexander Best wrote: > On Fri Oct 14 11, Poul-Henning Kamp wrote: > > In message <20111014085609.GA3799@freebsd.org>, Alexander Best writes: > > > > >1) would it be possible to prepend those timestamps to the actual console > > >output and not only to the output of demsg? maybe via a sysctl toggle? > > > > The kernel does not know enough about timezones to emit anything > > but UTC timestamps. > > hmm ok. > > > > > >2) my dmesg output contains a lot of these entries: "<118>" > > > > These are magic markers for syslogd(8) specifying priority. > > it would be nice, if their output could be turned off via a dmesg flag imo. > > > > > >3) roughly the first 30 lines of my dmesg output have the timestamp "[1.0]". > > >would it be possible to have more accuracy there? > > > > No, because we don't know the time until we've found the RTC chip. > > maybe prepending the output with [??] instead of [1.0] would make more sense, > so users knows that those timestamps are bogus. or even better: if timestamp == 1.0 then simply don't ouput it at all. > > cheers. > alex > > > > > -- > > Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 > > phk@FreeBSD.ORG | TCP/IP since RFC 956 > > FreeBSD committer | BSD since 4.3-tahoe > > Never attribute to malice what can adequately be explained by incompetence.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20111014093613.GA15025>