The --copy-unsafe-links option cann't take affect. when I run : [root@beijingdb mms]#/usr/local/rsync/bin/rsync --copy-unsafe-links -vzrtopgn --progress db@192.168.0.2::db /mnt/sdb7/77dbmysqldata --password-file=/usr/ local/rsync/etc/dbpass I get the following error at tail of output : wrote 1035 bytes read 35847 bytes 24588.00 bytes/sec total size is 6755588056 speedup is 183167.62 rsync warning: some files vanished before they could be transfered (code 24) at main.c(1048) In my server log,I get : 2004/08/11 12:19:23 [2912] rsync on db from db@beijingdb (192.168.0.12) 2004/08/11 12:19:23 [2912] file has vanished: "/phpinfo.php" (in db) 2004/08/11 12:19:23 [2912] file has vanished: "/mms/Downmmslog.MYI" (in db) 2004/08/11 12:19:23 [2912] file has vanished: "/mms/Downmmslog.MYD" (in db) 2004/08/11 12:19:23 [2912] file has vanished: "/mms/Downmmslog_20040420.frm" (in db) 2004/08/11 12:19:23 [2912] file has vanished: "/mms/Downmmslog_20040420.MYD" (in db) 2004/08/11 12:19:23 [2912] file has vanished: "/mms/Downmmslog_20040420.MYI" (in db) 2004/08/11 12:19:23 [2912] file has vanished: "/mms/Downmmslog_20040621.frm" (in db) 2004/08/11 12:19:23 [2912] file has vanished: "/mms/Downmmslog_20040621.MYD" (in db) 2004/08/11 12:19:23 [2912] file has vanished: "/mms/Downmmslog_20040621.MYI" (in db) 2004/08/11 12:19:23 [2912] wrote 35847 bytes read 1035 bytes total size 6755588056 2004/08/11 12:19:23 [2912] rsync warning: /mms/Downmmslog.MYI is a symbolic links that point outside the copied tree. why i get "some files vanished before they could be transfered (code 24) at main.c(410)"? Is this a bug of copy-unsafe-links?
You must be running the daemon with chroot enabled, making it impossible to follow a symlink outside the module's root path. Your only choices are to disable chroot (see the rsyncd.conf man page) or to make the symlinks relative links to content inside the chrooted area. The CVS version of rsync outputs a better error than the misleading "file has vanished" one that 2.6.2 outputs, so it would at least have told you that the symlink was invalid.