On Saturday, May 27, 2006 11:32:09 PM -0500 Paul Johnson <[EMAIL PROTECTED]> wrote:
We use AFS to store backups of locally stored files on Linux systems. I've been trying to automate this by scripting with rsync or showing the users how to use unison. However, there is some trouble because the files on the AFS system appear to be owned by a user "sync" and so rsync thinks that every file has the wrong permissions.
The files will be owned by the (AFS) user that created them. Only an AFS administrator can change the owner of a file. As long as you are not running rsync as root, it should not attempt to preserve owners, so this shouldn't be a problem.
I use both rsync and unison with AFS on a fairly regular basis, and both tools behave exactly as expected.
$ rsync -e ssh -r ~/.Config_Backups/GNUstep /afs/ku.edu/usr/pols/pauljohn/LabNotes rsync error: received SIGUSR1 or SIGINT (code 20) at rsync.c(179) rsync: writefd_unbuffered failed to write 69 bytes: phase "unknown" [generator]: Broken pipe (32) rsync error: error in rsync protocol data stream (code 12) at io.c(1099)
OK, so something sent SIGINT or SIGUSR1 to one of your rsync processes, which caused it to exit, confusing the thing at the other end of the pipe. You should figure out what that is. This sounds like a problem with rsync, not AFS.
_______________________________________________ OpenAFS-info mailing list [email protected] https://lists.openafs.org/mailman/listinfo/openafs-info
