Date: Wed, 03 Nov 2004 20:02:54 +0100 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net> Cc: cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/dev/em if_em.c Message-ID: <24243.1099508574@critter.freebsd.dk> In-Reply-To: Your message of "Wed, 03 Nov 2004 18:57:23 GMT." <Pine.BSF.4.53.0411031845440.1747@e0-0.zab2.int.zabbadoz.net>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <Pine.BSF.4.53.0411031845440.1747@e0-0.zab2.int.zabbadoz.net>, "Bjoern A. Zeeb" writes: >On Wed, 3 Nov 2004, Poul-Henning Kamp wrote: > >> In message <Pine.BSF.4.53.0411031818150.1747@e0-0.zab2.int.zabbadoz.net>, "Bjoern A. Zeeb" writes: >> >> >I think it's overkill to enable all verbose msgs just to see link state >> >messages in my logs again when someone fiddles at the cabling in the >> >colo hotel where he shouldn't - or did I mis-read the commit message ? >> >> Link states are visible with ifconfig(8). > >of course they are but who will notify me or write them to my logs so >I have timestamps ? Do I need to write a small daemon to regularly >and fast enough poll for link state changes now ? I'm not against logging link states, but if we do it, we should not arbitrarily limit it to when the link is gigE. In general I would say it is a job for SNMP. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?24243.1099508574>