Re: kqueue and resource forks
site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com -steve On Sep 10, 2009, at 8:11 PM, Terry Lambert wrote: This is on a normal HFS+ volume, so it's not doing the ._ file You have it backwards. _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.appl... I just reinstalled 10.5 and XCode and tested it. It definitely worked on 10.5 and now does not work on 10.6 The Finder seems to update, so it must be detecting the change somehow, but I can't get it working on 10.6 using the same code that worked on 10.5 Could you test this over there to see? If you set the file's Open With settings in the finder it will add a resource fork. Set up a test app to watch that file with kqueues and it shouldn't fire on 10.6. I used both my code and Google toolbox's kqueue code. Both were the same. On Sep 10, 2009, at 4:30 PM, Steve Gehrman wrote: I'm pretty sure this worked in 10.5. One 10.6 i set kqueues to watch a file. If I modify the resource fork or add or delete the fork, the kqueue event doesn't fire and I don't get notified to update. Anyone know if this was a change in 10.6? I don't remember getting bug reports for my 10.5 builds. I'm pretty sure this did not work in 10.5, except on UFS, and that doesn't natively support resource forks. In 10.6, we actually added support for a lot of FS-level kevents at the VNOP_ KPI layer, which means that they'll apply to all filesystems equally, but probably still not resource forks individually (part of the removal of UFS support was to support these events for programs that needed them on non-UFS FS types. If you are getting errors now, it's probably because you asked for events before that it was impossible for you to get except on UFS in 10.5, and now you are getting them for HFS+, and aren't reacting correctly to them occurring. Generally, if something doesn't work, you shouldn't be asking for it in old software, in case it starts working in new software. I expect if you were to try this on 10.5 on UFS, you'd see the same sort of things. -- Terry This email sent to site_archiver@lists.apple.com
participants (1)
-
Steve Gehrman