From owner-freebsd-arch Mon Nov 26 13:23: 6 2001 Delivered-To: freebsd-arch@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 5D69737B417; Mon, 26 Nov 2001 13:23:03 -0800 (PST) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 26 Nov 2001 21:23:02 +0000 (GMT) To: Kris Kennaway Cc: Robert Watson , arch@FreeBSD.org Subject: Re: cvs commit: src/usr.bin/tail forward.c In-Reply-To: Your message of "Sun, 25 Nov 2001 15:05:31 PST." <20011125150531.A93698@xor.obsecurity.org> Date: Mon, 26 Nov 2001 21:23:01 +0000 From: Ian Dowse Message-ID: <200111262123.aa20504@salmon.maths.tcd.ie> Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <20011125150531.A93698@xor.obsecurity.org>, Kris Kennaway writes: > >It would be nice if this could be abstracted somehow so the >application doesn't have to do both. Most application writers are >going to forget this. Yes, it would be nice to have some sort of conversion layer that used polling of the underlying filesystem to allow use of the kqueue API even when active notification is not directly available. There would of course be a trade-off between efficiency and timely notifications; maybe some sort backoff algorithm for polling would give acceptable results. I'm not sure I'd like to see what would happen if an application that expects to be able to monitor hundreds of files efficiently was to try to do this over NFS though :-) Ian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message