Hi,
did you ever test out if using "mount --bind" instead of symlinking
does solve the problem? That would be the simplest thing.
Apart from that I have 2 other ideas that could solve this problem (in
case someone wants to write a patch for this):
Use find --follow with:
1.) when checking existing files recursivly resolve each symlinked
directory and record the real path.
2.) record the inode number of every file that is suposed to be there
and delete files with unknown inodes.
The 2nd option is a variant of the first that would cut down memory
requirements. Inode numbers are a lot smaller than the full path of
each file.
MfG
Goswin
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
