Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 12 Sep 1999 10:56:42 -0700 (PDT)
From:      John Polstra <jdp@polstra.com>
To:        wollman@khavrinen.lcs.mit.edu
Cc:        current@freebsd.org
Subject:   Re: An FS question perhaps... non blocking I/O.
Message-ID:  <199909121756.KAA38620@vashon.polstra.com>
In-Reply-To: <199909091954.PAA13059@khavrinen.lcs.mit.edu>
References:  <Pine.BSF.4.05.9909092224510.15440-100000@pena.oh5nxo.ampr.org> <000601befafb$83fbb8c0$291c453f@kbyanc.alcnet.com> <199909091954.PAA13059@khavrinen.lcs.mit.edu>

next in thread | previous in thread | raw e-mail | index | archive | help
In article <199909091954.PAA13059@khavrinen.lcs.mit.edu>,
Garrett Wollman  <wollman@khavrinen.lcs.mit.edu> wrote:

[POLLEXTEND, POLLATTRIB, POLLNLINK, POLLWRITE]

> It is probably undocumented.  I was a bit reluctant to document it
> since I know that the interface is not correct.  One of these days,
> I (or more likely some enterprising young hacker) will fix it.

Just to avoid duplicated effort:  I currently have work in progress
on a "fslog" pseudo-device.  It enables you to monitor a filesystem
and receive notifications for all interesting changes to files and
directories.  This includes reads, writes, renames, file creations,
unlinks, links, etc. -- anything that changes the stat(2) results
for a file, or causes directory entries to be created, destroyed, or
changed.  The device itself is working, but so far I have implemented
the support for only a few of the event types.  It won't take much
more work to finish it.

My personal interest is to allow a CVSup master server to avoid
doing a tree walk whenever a client connects.  I want to provide the
functionality of the old "supscan" utility, but in real time.

John
-- 
  John Polstra                                               jdp@polstra.com
  John D. Polstra & Co., Inc.                        Seattle, Washington USA
  "No matter how cynical I get, I just can't keep up."        -- Nora Ephron


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199909121756.KAA38620>