Re: [PATCH] time limit
Jan-Benedict Glaw wrote: I have written a patch for rsync-2.6.1pre-2 which adds a --time-limit=T option. When this option is used rsync will stop after T minutes and exit. I think this option is useful when rsyncing a large amount Okay, nice thing. What about $ echo killall rsync | at midnight Of couse, you can make that a bit more flexible if you've got several concurrent rsync running (by using their PID and checking it before killing it to actually be a rsync instance)... That's more or less the ugly hack referred to previously. It does work as expected, but personally, I'd rather there were a native rsync method of achieving this. Less kludgy. DJFM -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: rsync error: some files could not be transferred (code 23) at main.c(1045)
[EMAIL PROTECTED] wrote: On Tue, Dec 23, 2003 at 04:00:24AM +0100, [EMAIL PROTECTED] May the file-list is getting a bit to big for rsync? If I splitt the transfer using for i in *; do rsync -avv --delete --delete-excluded server::public/$i dest/ done it works seamlessly. The file list is about 50 files long. This brings up something I've been wondering about. If I were to compose a list of files and pass them to rsync one at a time, what sort of overhead would this entail as opposed to simply pointing rsync to a directory containing those files? -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Change one file, and they all get sent!
Steve Howie wrote: Hi, Just starting out with rsync, and I think I might be missing a fundamental point of how it works. Is either box Windows? When I used an NT4 server as my rsync server, I had to use --modify-window 2 on the client side to get it to NOT copy over all files. Daemian Mack Scenario: I start an rsync daemon on host A, and define a module 'test' on the rsyncd.conf file. 'test' is essentially my home directory on host A I then sign on to host B and issue rsync --progress --recursive --links --stats arthur::test/ /var/tmp/haggis This copies 'test' from host 'arthur' (host A) into /var/tmp/haggis (on host B) so far so good. Everything goes to host B no problem. Next I edit a small file in 'test' on host A, then reissue the rsync command above. All files are checked and transferred according to the summary at the end. Am I incorret in assuming that only the delta of the before and after of the one small file I edited would be sent, rather than the entire directory tree defined by 'test'? Remember, I'm using rsync to copy *from* a host running an rsync daemon...would this be the issue? Confused and probably missing something simple any ideas? Thanks! Scotty -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: [rsync-announce] rsync security advisory
[EMAIL PROTECTED] wrote: rsync 2.5.6 security advisory - December 4th 2003 Background -- The rsync team has received evidence that a vulnerability in rsync was recently used in combination with a Linux kernel vulnerability to compromise the security of a public rsync server. While the forensic evidence we have is incomplete, we have pieced together the most likely way that this attack was conducted and we are releasing this advisory as a result of our investigations to date. Would this be the rsync.gentoo.org box that was compromised on 12-02? Daemian Mack -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Size Limit in rsyncd.conf File?
jw schultz wrote: I've not tried it but auth users permits the use of shell wildcards in user names so auth users = * would restrict the users to all of those listed in the secrets file. If you wish different user lists for different modules just use module-specific secrets files. That would be a little clumsy for me, since there are no easily-defined sets of users I could enable and disable conveniently. However, the shell wildcards you mention are going to solve my problem, I think. What I've done is set auth users = [^#]* which takes rsyncd.conf out of the loop when enabling/disabling user accounts; now I can just prepend a # to an account in rsyncd.secrets to disable it and remove that hash to enable the account. So far, this seems to be working great for me. Thanks for your help! Daemian Mack -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
