Date: Tue, 22 Nov 2022 09:34:50 -0600 (CST) From: Dan Mack <mack@macktronics.com> To: Warner Losh <imp@bsdimp.com> Cc: freebsd-current@freebsd.org Subject: Re: dmesg content lifetime Message-ID: <6146841c-baef-134-dcd9-30db2d92732@macktronics.com> In-Reply-To: <CANCZdfq9Q%2BpRBo1HvTDgHcQ6ytMA%2BzZ0DqVx_2E=GoZuBOqWdQ@mail.gmail.com> References: <9d519f-ce87-72d-dc6-789817468974@macktronics.com> <CANCZdfq9Q%2BpRBo1HvTDgHcQ6ytMA%2BzZ0DqVx_2E=GoZuBOqWdQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
It disappears a piece at a time - the oldest entries disappear first. However, it vanishes even when there are only 2-3 lines in it so I didn't think capacity was in play as I expected. So for example I might see a rate-limit entry from someone spamming the system and then it will usually be gone in a couple days and the buffer is completely empty. Similarly if I do something like ifconfig em0 down; ifconfig em0 up ; it's logged but disappears after a day or so. I'm looking to see if this is just a cron job or something clearing it as it might be user-error on my part. Also this is an older system so I'll probably look at it again after I update. Thank you, Dan On Tue, 22 Nov 2022, Warner Losh wrote: > On Tue, Nov 22, 2022 at 8:13 AM 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? >> > > It already is a fixed memory size. Do you see it all disappear at once, or > over time? > > Warner >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6146841c-baef-134-dcd9-30db2d92732>