That brings up an interesting question.. So far, all of the WAN rsync's I do use an SSH tunnel, and not the rsync daemon on the server end. However, while doing an rsync, I notice the "rsync --server" process running on the source box. Will the below flag "ignore nonreadable = true" in /etc/rsyncd.conf still work?
I use this syntax on the receiving/initiating end: rsync -avzpogDt --force -e "ssh -i /root/.ssh/example_key " somehost:/backup/public /backup/somehost Dave -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Eberhard Moenkeberg Sent: Monday, March 28, 2005 3:54 PM To: rsync@lists.samba.org Subject: Re: Skipping unreadable files Hi, On Mon, 28 Mar 2005, C. P. wrote: > Is there a way to skip unreadable files so rsync doesnt die? > > i have to rsync live filesystems and sometimes a file is open and blocked > (outlook.pst) and rsync says: > > rsync error: received SIGUSR1 or SIGINT (code 20) at rsync.c(229) > > instead of skipping it. > > I understand that --ignore-errors isnt what i need. I tried it anyway. You have to do it on the server side, with ignore nonreadable = true in /etc/rsyncd.conf. Cheers -e -- Eberhard Moenkeberg ([EMAIL PROTECTED], [EMAIL PROTECTED]) -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html