On Wed, 12 Jul 2006, Ray Lee wrote:
> > > For the syslog spamming, you could jus emit the message once when the
> > > state is first noticed, then emit a everything good message when it
> > > clears up. There's no need to log it repeatedly during the problem
> > > period.
> >
> > That's almost exactly how the driver behaves currently -- the message is
> > printed just once when the state is first noticed. Nothing is printed
> > when the state is cleared, and nothing gets printed repeatedly during the
> > problem period. But then the problem recurs very quickly.
>
> Then the logging of the 'all cleared up' message would be better if it
> had a bit of hysteresis to it -- the good state is noticed, but don't
> log it as such until it hangs out there for a while and has had a
> chance to quiesce.
You didn't read what I wrote -- there _is_ no "all cleared up" message.
Alan Stern
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
