Re: CatalogSearch behaving oddly on various AFP volumes
Re: CatalogSearch behaving oddly on various AFP volumes
- Subject: Re: CatalogSearch behaving oddly on various AFP volumes
- From: Thomas Tempelmann <email@hidden>
- Date: Mon, 9 Mar 2009 13:23:14 +0100
One more interesting detail on FSCatalogSearch returning -1304:
This error always occurs on the very first invocation of
FSCatalogSearch. This indicates that the iterator would be somewhat
invalid. But since this only happens depending on states with that
particular remote system, it's very unlikely that it's an error on my
side, as it often works, even on other remote volumes of different
systems at the same time.
If it were a "normal" catalog change during the search, noErr would be
returned and the containerChanged flag would be set instead.
So the question is basically: what can cause a -1304 error on a remote
volume, maybe related to when / how / in which order it was mounted?
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Filesystem-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden