Re: Using KAuth for Monitoring File Operations
site_archiver@lists.apple.com Delivered-To: darwin-kernel@lists.apple.com --Amanda _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-kernel mailing list (Darwin-kernel@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-kernel/site_archiver%40lists.a... On Jun 15, 2007, at 9:45 AM, Michael Smith wrote: If your product's aim is to have a complete backup copy of everything, then you are better off waiting in the FILEOP scope for last-close notifications with the modified flag set. This gives you both the indication that the file is not being modified, and an indication that it previously has been. Right--but this is doing the copy after each modification (so you'll have it already saved away when the next modification happens), not on-demand just before the change, which is what Yogesh was asking for. But you're quite right--if you're willing to do "backup just after each change" instead of "backup just before each change", hooking FILEOP scope in a Kauth module works very well. This email sent to site_archiver@lists.apple.com
participants (1)
-
Amanda Walker