On Wed, 23 Nov 2022 07:16:19 +0900
Tomoaki AOKI wrote:
> On Tue, 22 Nov 2022 19:13:18 +0100
> Gary Jennejohn 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
On Tue, 22 Nov 2022 19:13:18 +0100
Gary Jennejohn wrote:
> On Wed, 23 Nov 2022 01:16:55 +0900
> Tomoaki AOKI wrote:
>
> > On Tue, 22 Nov 2022 09:47:10 -0600 (CST)
> > Dan Mack wrote:
> >
> > > On Tue, 22 Nov 2022, Alexander Kabaev wrote:
> > >
> > > > On Tue, 22 Nov 2022 09:12:28 -0600 (CST)
>
On Tue, 22 Nov 2022, Rodney W. Grimes wrote:
On 22 Nov 2022, at 9:34, Dan Mack wrote:
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 mi
> On 22 Nov 2022, at 9:34, Dan Mack wrote:
>
> > 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
On Wed, 23 Nov 2022 01:16:55 +0900
Tomoaki AOKI wrote:
> On Tue, 22 Nov 2022 09:47:10 -0600 (CST)
> Dan Mack wrote:
>
> > On Tue, 22 Nov 2022, Alexander Kabaev wrote:
> >
> > > On Tue, 22 Nov 2022 09:12:28 -0600 (CST)
> > > Dan Mack wrote:
> > >
> > >> It seems like dmesg content ages out over
On Tue, Nov 22, 2022 at 8:49 AM Mike Karels wrote:
> On 22 Nov 2022, at 9:34, Dan Mack wrote:
>
> > 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.
> >
> >
On Tue, 22 Nov 2022 09:47:10 -0600 (CST)
Dan Mack wrote:
> On Tue, 22 Nov 2022, Alexander Kabaev wrote:
>
> > On Tue, 22 Nov 2022 09:12:28 -0600 (CST)
> > Dan Mack wrote:
> >
> >> It seems like dmesg content ages out over time. Is there a way to
> >> leave the contents based on a fixed memory
On 22 Nov 2022, at 9:34, Dan Mack wrote:
> 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
On Tue, 22 Nov 2022, Alexander Kabaev wrote:
On Tue, 22 Nov 2022 09:12:28 -0600 (CST)
Dan Mack 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
On Tue, 22 Nov 2022 09:12:28 -0600 (CST)
Dan Mack 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 sequ
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 b
On Tue, Nov 22, 2022 at 8:13 AM Dan Mack 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
12 matches
Mail list logo
