With much hope I upgraded to rsync version 2.5.6 in hopes that it would
correct the symbolic link bug I have been wrestling with...
No dice. It still insists on dropping the leading slash from a symbolic
link outside the source tree. Interactively it still works fine, but as
a daemon it's busted.
I have an administrative server that I use to rsync data between two
hosts. It has root access to our fileserver but does not mount
directories using the same paths as a client machine. In some
directories I have symbolic links that are invalid on the admin server,
but valid on a client (due to
If I remove a directory 'foo' and create a file foo, and then do a resync from a
remote server
with the -u flag, the file will be replaced by the directory, even though
the file is newer than the directory. Is this a bug, or a feature?
--
Karl A. Wieman voice: 212-409
