In article <[EMAIL PROTECTED]>,
Garrett Wollman <[EMAIL PROTECTED]> 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 [EMAIL PROTECTED]
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 [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
