search for: rsyncpath

...s from a server and need to be sure to have a consistent semantics in what version of the file appears in the local directory. I stripped our sitation down to a (yet fairly complex) test archive, so you can reproduce the situation. Here is the script, which is also in the archive: #!/bin/bash rsyncpath=rsync $rsyncpath -av --delete dir1/ dir2/ merged12 $rsyncpath -av --delete dir1/ dir2/ dir3/ merged123 # as dir3 only consists of an empty dir "subdir" we expect # that merged12 and merged123 have identical files in them # but merged*/subdir/s0/LOOKATTHIS differ as they come from differ...

...s sudoers line: Cmnd_Alias BACKUPCOMMANDS = /usr/bin/rsync I call puppet like this: puppetd --factsync --server=xxx.yyy.61.131 --waitforcert 60 --test the recipe is: sudoensure_line { sudobackupcommands: ligne => "Cmnd_Alias BACKUPCOMMANDS = $rsyncpath", before => sudoensure_line["sudoaqbackup"] } sudoensure_line { sudoaqbackup: ligne => "aqbackup ALL = NOPASSWD: BACKUPCOMMANDS" } after two run of puppetd i end like this : Cmnd_Alias...

...a consistent semantics in what version of the file > appears in the local directory. > > I stripped our sitation down to a (yet fairly complex) test archive, so you > can reproduce the situation. > > Here is the script, which is also in the archive: > > #!/bin/bash > rsyncpath=rsync > $rsyncpath -av --delete dir1/ dir2/ merged12 > $rsyncpath -av --delete dir1/ dir2/ dir3/ merged123 > # as dir3 only consists of an empty dir "subdir" we expect > # that merged12 and merged123 have identical files in them > # but merged*/subdir/s0/LOOKATTHIS differ...

...ore AssignedTo: wayned@samba.org ReportedBy: carnesresearchcenter@gmail.com QAContact: rsync-qa@samba.org If I execute the following command: rsync -vrptgz --rsh="ssh $BCPSERVER rsync rsyncd --daemon -- config=$RSYNCDCONFIGFILE --port=$RSYNCDPORT" --rsync-path=$RSYNCPATH $RSYNCSOURCE $LOGNAME@$BCPSERVER::$RSYNCDESTINATIONMODULE and I have a symbolic link in the directory represented by $RSYNCSOURCE then I get the following output: building file list ... 5 files to consider overflow: linkname_len=1862797370 ERROR: buffer overflow in receive_file_entry rsync e...

...ore AssignedTo: wayned@samba.org ReportedBy: carnesresearchcenter@gmail.com QAContact: rsync-qa@samba.org If I execute the following command: rsync -vrptgz --rsh="ssh $BCPSERVER rsync rsyncd --daemon -- config=$RSYNCDCONFIGFILE --port=$RSYNCDPORT" --rsync-path=$RSYNCPATH $RSYNCSOURCE $LOGNAME@$BCPSERVER::$RSYNCDESTINATIONMODULE and I have a symbolic link in the directory represented by $RSYNCSOURCE then I get the following output: building file list ... 5 files to consider overflow: linkname_len=1862797370 ERROR: buffer overflow in receive_file_entry rsync e...

https://bugzilla.samba.org/show_bug.cgi?id=2784 ------- Additional Comments From carnesresearchcenter@gmail.com 2005-06-09 11:20 ------- *** Bug 2785 has been marked as a duplicate of this bug. *** -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

Greetings all. Due to security concerns we are switching our backup processes from "SSH tunnel to rsync daemon" to "Running rsync over ssh in --server mode". In daemon mode we had a nice conglomerate log file of all of the backups that ran. Now that I am tweaking the scripts to run over --server mode I see that by default there is no remote logging. From what I have read on