Directory change journals rather then flushing the directory cache?
 

With the current version of ioFTPD (Beta-5.8), when ever an external script makes a file/directory related change, the affected directory and/or it's entire sub-tree must be flushed (using shared memory's DC_DIRECTORY_MARKDIRTY), in order for ioFTPD to updates its internal cache. What about using change journals to update the modified directory 'smartly'? That way, only the related portions of the cache are updated. However, I'm not sure about the 'possible' performance implications involved. The downside is that it's an NTFS-only feature.

Just a thought. :)

For those of you who aren't familar with 'change journals':
http://msdn.microsoft.com/library/en...e_journals.asp
http://msdn.microsoft.com/library/en...rychangesw.asp