Unspecified behaviour whilst rec

[GoogleCodeExporter]

Unspecified behaviour whilst rec

[GoogleCodeExporter]

Oops sent that a little early :P

It would seem to me there is a bug in the OSX implementation for which I am 
seeing files removed and re-added when neither the file has been moved or 
altered, yet another file has been added.

If an unknown entry is seen then rescan is called which iterates over the 
directory with readdir yet during this iteration files descriptors can be 
opened or closed, does this not invalidate the descriptors for the next readdir 
? and should it not be using telldir and seekdir ?

Liam

Original comment by [email protected] on 19 Jul 2012 at 9:14

[GoogleCodeExporter]

Actually now that I have looked more into it this doesn't seem to be the 
problem (although I am still not sure about closing fd's when this would have 
been the last handle to it), I think it has more to do with the order of 
readdir when compared to the sorted cached entries. As far as I can see in the 
docs, the order of entries returned by readdir is not deterministic. If this is 
the case maybe it needs to cache the entries and sort before acting upon them?

Liam

Original comment by [email protected] on 19 Jul 2012 at 9:50