> I'd implement this via LD_PRELOAD library [ ... ] > > There's a problem with sync-on-close anyway - mmap for file I/O. Who > guarantees you no file contents are being modified after the close() ?
The latter is actually a good argument for doing this (if it is necessary) in the file system, rather than via a preload library. The file system knows when the file is no longer accessible by a user process (neither opened nor mapped). That said, I’m not sure exactly what this buys you for disk replication. What’s special about files which have been closed? Is the point that applications might close a file and then notify some other process of the file’s availability for use? This message posted from opensolaris.org _______________________________________________ zfs-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
