Date: Tue, 22 Nov 2022 09:47:10 -0600 (CST) From: Dan Mack <mack@macktronics.com> To: Alexander Kabaev <kabaev@gmail.com> Cc: freebsd-current@freebsd.org Subject: Re: dmesg content lifetime Message-ID: <c4272589-572a-26a1-7e1e-6ffbe66fc615@macktronics.com> In-Reply-To: <20221122104445.4ed88f6f@kan> References: <9d519f-ce87-72d-dc6-789817468974@macktronics.com> <20221122104445.4ed88f6f@kan>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 22 Nov 2022, Alexander Kabaev wrote: > On Tue, 22 Nov 2022 09:12:28 -0600 (CST) > Dan Mack <mack@macktronics.com> wrote: > >> It seems like dmesg content ages out over time. Is there a way to >> leave the contents based on a fixed memory size instead? >> >> Dan >> > I think this is how it works: the kernel message bugger is of fixed > size and kernel and syslog sequences (dmesg -a) share it. The other > syslog users eventually puts enough content in there to displace all of > kernel messages. If the kernel stays quiet, 'dmesg' then returns > nothing, as by default it filters syslog entries that do not KERN > facility out, see sbin/dmesg/dmesg.c. > > -- > Alexander Kabaev > Thank you Alexander, I did not know this. I'll USL (use-the-source-luke) :-) Dan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?c4272589-572a-26a1-7e1e-6ffbe66fc615>