#5 Support for Distributed Link Tracking Services


This is a very nice implementation of a sorely needed capability.

I have noticed that a few move/rename operations get missed with the current methods of intercepting Move and Rename operations on target directories. Renaming a directory that is on the direct path of a target directory is not trapped. Moving a directory containing multiple target directories may generate many messages and can be problematic if other move errors occur. Would it be possible to support tracking of linked target directories using the Microsoft Distributed Link Tracking Service?


  • Michael Elsdoerfer

    Logged In: YES
    Originator: NO

    Thanks for the suggestion, I didn't know about the service so far. I'll try to find the time to investigate.

  • wellread1

    wellread1 - 2007-08-03

    Logged In: YES
    Originator: YES

    It seems the Directory Link Service provides link tracking for shortcuts and OLE objects only. Nonetheless, I think one can make use of this service by creating shortcuts pointing to the source directory for each reparse point. If one names each shortcut after the GUID of the reparse point and keeps it in a protected directory, it should be possible to use the IShelllink::Resolve Method (which takes advantage of the Directory Link Service) to recover the path to the source for any broken reparse point. This procedure would add only 1kb (for each shortcut) of storage overhead for each reparse point. It should also be possible maintain sufficient independent data to rebuild the the shortcuts if they were inadvertently deleted, so the entire procedure could be fairly robust.


Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks