--XLRYXLjFvhZHhWey
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, May 02, 2006 at 09:59:05AM +0200, joerg@britannica.bec.de wrote:
> > Other than being somewhat annoying, do they serve any useful
> > purpose?  If there any problem if "#ifdef DEBUG"ing them in
> > if_link_state_change()?
>=20
> I was thinking about that as well, when I initially changed the code to
> use the common functions. I'd suggest to place it under bootverbose,
> but that's just an opinion. It is helpful to find flacky links, but can
> be achieved with different means.

It can, but you need to know to be looking.  You can watch the routing
socket (or a number of other places) if you suspect something is wrong,
or have a particular reason to go to the effort to actively monitor
this information.

However, I find/found the messages handy more as an alert of something
awry, or a clue when going back through logs chasing what may have
manifested as some other problem.  It was one of the small things I
missed from SunOS, way back when.

Now, some of the spurious cases could be supressed to make it less
annoying, and perhaps the message could be less intrusive (set at a
level where it goes to syslog but not disrupt the console), but I
still think they'd be handy to keep. Or, to have kept, as it turns
out, even if they did start appearing more as a side-effect of another
change than as a deliberate choice.

--
Dan.

--XLRYXLjFvhZHhWey
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (NetBSD)

iD8DBQFEVyGxEAVxvV4N66cRAiCwAJ4xbsfvUdXT+ZyrcuyKCQQOmnR8GwCgjfnA
q8y7vu5enxQP2CuzZbDVejc=
=9F87
-----END PGP SIGNATURE-----

--XLRYXLjFvhZHhWey--