I think it is a pretty valid question(request?), you have to relay on
external mechanisms, like syslog, or to compare differences from previous
outputs of dmesg.
On HP-UX dmesg has the optional parameter '-' which:
system tables overflow or the system crashes). If the - argument is
specified, dmesg computes (incrementally) the new messages since the
last time it was run and places these on the standard output. This is
typically used with cron (see cron(1)) to produce the error log
/var/adm/messages by running the command:
On FreeBSD and Linux it can be cleared.
I think it is a feature that can help a lot.
On 7/4/07, Nick Guenther <[EMAIL PROTECTED]> wrote:
>
> On 7/4/07, smonek <[EMAIL PROTECTED]> wrote:
> > > > > >
> > > > > > On FreeBSD i have 'sysctl kern.msgbuf_clear' bu OpenBSD don't
> > > > > > have this options
> > > > >
> > > > > find a clean one here: /var/run/dmesg.boot
> > > > >
> > > > > HTH,
> > > > >
> > > > > Timo
> > > >
> > > > This now work
> > >
> > > cool! :)
> > sorry not work :-(
>
> I think what he's getting at is that there's no way to clear the dmesg
> buffer, but that if you need a clean dmesg from-boot, you can open
> /var/run/dmesg.boot
>
> Why do you need to clear the dmesg?
>
>
--
You should be the change that you want to see in the world.
- Gandhi
