Ivan Voras wrote:
Hi,
Im thinking again of the old idea of implementing poor man's file
replication system using kqueue to monitor changes on files.
I made something with the idea, available here:
http://ivoras.sharanet.org/stuff/adfs.tgz
It was hacked up over the weekend and probably contai
On Mon, 2 Jun 2008 21:07:15 -0400, Garance A Drosihn <[EMAIL PROTECTED]> wrote:
> At 12:33 AM +0200 6/3/08, Kris Kennaway wrote:
>>Ivan Voras wrote:
>>>Suleiman Souhlal wrote:
>>>
I have an old patch that makes kqueue monitor every file write on
the system and return the inode number in t
On Tue, 3 Jun 2008, Kris Kennaway wrote:
I think there's also considerable overlap with other kernel event systems,
such as audit, and we might benefit from thinking seriously about enhancing
those event systems rather than introducing a new one. The design of
fsevents is pretty much entirel
Robert Watson wrote:
fsevents allows user processes to subscribe, effectively on a
per-filesystem basis, to namespace and file close operations.
...
I think there's also considerable overlap with other kernel event
systems, such as audit, and we might benefit from thinking seriously
about e
On Mon, 2 Jun 2008, Garance A Drosihn wrote:
I remember a discussion of changes to MacOS10 in Leopard which made it
easier to implement features such as Spotlight and TimeMachine. The
description starts here, I think:
http://arstechnica.com/reviews/os/mac-os-x-10-5.ars/7
the section on file
At 12:33 AM +0200 6/3/08, Kris Kennaway wrote:
Ivan Voras wrote:
Suleiman Souhlal wrote:
I have an old patch that makes kqueue monitor every file write on
the system and return the inode number in the knote's data field:
http://people.freebsd.org/~ssouhlal/testing/kqueue-anyvnode-20050503.dif
Ivan Voras wrote:
Suleiman Souhlal wrote:
I have an old patch that makes kqueue monitor every file write on the
system and return the inode number in the knote's data field:
http://people.freebsd.org/~ssouhlal/testing/kqueue-anyvnode-20050503.diff
.
I'd think it shouldn't be too hard to mak
Suleiman Souhlal wrote:
I have an old patch that makes kqueue monitor every file write on the
system and return the inode number in the knote's data field:
http://people.freebsd.org/~ssouhlal/testing/kqueue-anyvnode-20050503.diff .
I'd think it shouldn't be too hard to make it per-mountpoint.
On May 28, 2008, at 7:46 AM, Oliver Fromme wrote:
Ivan Voras wrote:
Im thinking again of the old idea of implementing poor man's file
replication system using kqueue to monitor changes on files.
It would be cool to have a kernel interface so you could
attach to a mountpoint and receive a log
2008/5/28 Oliver Fromme <[EMAIL PROTECTED]>:
> Ivan Voras wrote:
> > Im thinking again of the old idea of implementing poor man's file
> > replication system using kqueue to monitor changes on files.
>
> It would be cool to have a kernel interface so you could
> attach to a mountpoint and receive
Ivan Voras wrote:
> Im thinking again of the old idea of implementing poor man's file
> replication system using kqueue to monitor changes on files.
It would be cool to have a kernel interface so you could
attach to a mountpoint and receive a log of all activity
on that file system. That's simi
11 matches
Mail list logo
