Date: Mon, 16 May 2005 14:31:36 +0200 From: Sebastien Petit <spe@phear.org> To: freebsd-net@freebsd.org Cc: jeremie@le-hen.org Subject: Re: SIOCGIFMEDIA problems Message-ID: <20050516143136.4dea9cb9.spe@phear.org> In-Reply-To: <20050516094309.GD777@obiwan.tataz.chchile.org> References: <20050513111013.41905e73.spe@phear.org> <m2wtq3cnkz.wl%gnn@neville-neil.com> <20050513191705.61d2b742.spe@phear.org> <20050516094309.GD777@obiwan.tataz.chchile.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 16 May 2005 11:43:09 +0200 Jeremie Le Hen <jeremie@le-hen.org> wrote: > Hi Sebastien, > > On Fri, May 13, 2005 at 07:17:05PM +0200, Sebastien Petit wrote: > > [...] > > as a side note, you may wish to use the kqueue(2) framework to watch > at link stat changes. The main advantage is that it will change the > way it works from a polling model to a notification model. One major > drawback in your situation (portable software) is that kqueue(2) only > exists in BSD world, not in Linux. > Hi Jeremie, As I can see in kqueue man, I can only monitor events by file descriptor (read/write), a process id, a signal or a timer (under NetBSD 2) How I can use it for monitoring link status change on a network card ? Regards, Sebastien. -- spe@b0l.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050516143136.4dea9cb9.spe>