Date: Tue, 22 Nov 2022 10:44:45 -0500 From: Alexander Kabaev <kabaev@gmail.com> To: Dan Mack <mack@macktronics.com> Cc: freebsd-current@freebsd.org Subject: Re: dmesg content lifetime Message-ID: <20221122104445.4ed88f6f@kan> In-Reply-To: <9d519f-ce87-72d-dc6-789817468974@macktronics.com> References: <9d519f-ce87-72d-dc6-789817468974@macktronics.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--Sig_/ImeeSaRkAnPSQSX=1cHYX=o Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable 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? >=20 > Dan >=20 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. --=20 Alexander Kabaev --Sig_/ImeeSaRkAnPSQSX=1cHYX=o Content-Type: application/pgp-signature Content-Description: Цифровая подпись OpenPGP -----BEGIN PGP SIGNATURE----- iL0EARECAH0WIQR0dKhH2/VQpfw+8iNDrPWMyb5dlgUCY3zubl8UgAAAAAAuAChp c3N1ZXItZnByQG5vdGF0aW9ucy5vcGVucGdwLmZpZnRoaG9yc2VtYW4ubmV0NzQ3 NEE4NDdEQkY1NTBBNUZDM0VGMjIzNDNBQ0Y1OENDOUJFNUQ5NgAKCRBDrPWMyb5d lpWbAKDQjgJPdILO4zm/hhcHUxb+TH46VwCfTexeYDaj7/ire5gpCGz4LeTvKZc= =6xPU -----END PGP SIGNATURE----- --Sig_/ImeeSaRkAnPSQSX=1cHYX=o--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20221122104445.4ed88f6f>