Ian> When I give the --exclude-if-present option to duplicity, it tries Ian> to locate that file underneath the symlink, even if Ian> --exclude-other-filesystems is given as well.
Alexander> of course, because in order to determine if the file exists, Alexander> all symlinks involved in its path need to be followed. the Alexander> symlinks need to be followed as well to determine if a Alexander> file/dir is on the same filesystem. Sorry, I don't get that. From where I stand, the dead simple (and correct) solution is to _never_ follow any symlinks, just record them (i.e. their existence and target) in the archive and then pass to the next directory entry. In effect, the traversal should only follow canonical paths. I guess an exception would be if a path containing a symlink is given on the command line (as the root of the traversal), but in that case I would find it acceptable for duplicity to issue a warning and transform the path internally into the canonical one. If you see something wrong with that, please explain. Thanks for the effort, i. -- Ian Zimmerman gpg public key: 1024D/C6FF61AD fingerprint: 66DC D68F 5C1B 4D71 2EE5 BD03 8A00 786C C6FF 61AD http://www.gravatar.com/avatar/c66875cda51109f76c6312f4d4743d1e.png Rule 420: All persons more than eight miles high to leave the court. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
