Date: Wed, 23 Nov 2022 11:56:07 +0100 From: Gary Jennejohn <garyj@gmx.de> To: freebsd-current@freebsd.org Subject: Re: dmesg content lifetime Message-ID: <20221123115607.0a3a8d80@ernst.home> In-Reply-To: <20221123071619.4d9fc5c297c165ad98cf343d@dec.sakura.ne.jp> References: <9d519f-ce87-72d-dc6-789817468974@macktronics.com> <20221122104445.4ed88f6f@kan> <c4272589-572a-26a1-7e1e-6ffbe66fc615@macktronics.com> <20221123011655.c6a00ee21636e45e8b4f3a69@dec.sakura.ne.jp> <20221122191318.1036bc1e@ernst.home> <20221123071619.4d9fc5c297c165ad98cf343d@dec.sakura.ne.jp>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 23 Nov 2022 07:16:19 +0900 Tomoaki AOKI <junchoon@dec.sakura.ne.jp> wrote: > On Tue, 22 Nov 2022 19:13:18 +0100 > Gary Jennejohn <garyj@gmx.de> wrote: > > Or look at /var/run/dmesg.boot. It doesn't get overwritten. > > > > It may be overwritten on reboot. > And there are dmesg.[today|yesterday] on /var/log/, too. > Rotated daily. > Yes, it definitely does get overwritten on reboot. But at least its contents are stable between boots. =2D- Gary Jennejohn
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20221123115607.0a3a8d80>