Re: AW: [rsync-announce] Rsync 2.6.4 released
What about talking English, so we can also understand what you say. I really thought there are English only groups. Thanks. But to stay on-topic, great job Wayne! I'm going to implement this version slowly in my environments and hopefully it operates as stable as 2.6.3 did :) I'm looking forward to use the new features, like logging, delete after (as mentioned below), keep-a-live etc. - Joost On Thursday 31 March 2005 09:46, Markus Kemkes wrote: Sorry, aber 2.6.4 ist ZIEMLICH GEIL. Da müssen wir mal die neuen schalterchen ausprobieren. (delete-after zum Beispiel) Ich lass Dich raus aus so was. Gruss Markus -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Rückruf: [rsync-announce] Rsync 2.6.4 released
On Thu 31 Mar 2005, Markus Kemkes wrote: Markus Kemkes möchte die Nachricht [rsync-announce] Rsync 2.6.4 released zurückrufen. Unfortunately it's not possible to cancel messages sent to a mailing list :-) Paul -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
RE: AW: [rsync-announce] Rsync 2.6.4 released
When using --cvs-exclude option rsync is unable to sync *.exe files. Its throwing the following error. [sender] excluding file Update.exe because of pattern *.exe any ideas? Regards, -janardhan. P.S. I am using rsync-2.6.3 version. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Joost van den Broek Sent: Thursday, March 31, 2005 1:35 PM To: rsync@lists.samba.org Cc: Markus Kemkes; rsync-announce@lists.samba.org Subject: Re: AW: [rsync-announce] Rsync 2.6.4 released What about talking English, so we can also understand what you say. I really thought there are English only groups. Thanks. But to stay on-topic, great job Wayne! I'm going to implement this version slowly in my environments and hopefully it operates as stable as 2.6.3 did :) I'm looking forward to use the new features, like logging, delete after (as mentioned below), keep-a-live etc. - Joost On Thursday 31 March 2005 09:46, Markus Kemkes wrote: Sorry, aber 2.6.4 ist ZIEMLICH GEIL. Da müssen wir mal die neuen schalterchen ausprobieren. (delete-after zum Beispiel) Ich lass Dich raus aus so was. Gruss Markus -- 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
RE: AW: [rsync-announce] Rsync 2.6.4 released
I could see the following from exclude.c static char default_cvsignore[] = /* These default ignored items come from the CVS manual. */ RCS SCCS CVS CVS.adm RCSLOG cvslog.* tags TAGS .make.state .nse_depinfo *~ #* .#* ,* _$* *$ *.old *.bak *.BAK *.orig *.rej .del-* *.a *.olb *.o *.obj *.so *.exe *.Z *.elc *.ln core /* The rest we added to suit ourself. */ .svn/; What are your suggestions? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Molumuri, Janardhan Sent: Thursday, March 31, 2005 3:15 PM To: Joost van den Broek; rsync@lists.samba.org Cc: Markus Kemkes; rsync-announce@lists.samba.org Subject: RE: AW: [rsync-announce] Rsync 2.6.4 released When using --cvs-exclude option rsync is unable to sync *.exe files. Its throwing the following error. [sender] excluding file Update.exe because of pattern *.exe any ideas? Regards, -janardhan. P.S. I am using rsync-2.6.3 version. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Joost van den Broek Sent: Thursday, March 31, 2005 1:35 PM To: rsync@lists.samba.org Cc: Markus Kemkes; rsync-announce@lists.samba.org Subject: Re: AW: [rsync-announce] Rsync 2.6.4 released What about talking English, so we can also understand what you say. I really thought there are English only groups. Thanks. But to stay on-topic, great job Wayne! I'm going to implement this version slowly in my environments and hopefully it operates as stable as 2.6.3 did :) I'm looking forward to use the new features, like logging, delete after (as mentioned below), keep-a-live etc. - Joost On Thursday 31 March 2005 09:46, Markus Kemkes wrote: Sorry, aber 2.6.4 ist ZIEMLICH GEIL. Da müssen wir mal die neuen schalterchen ausprobieren. (delete-after zum Beispiel) Ich lass Dich raus aus so was. Gruss Markus -- 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 -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: patch for replacing non-printable chars in filenames
Hi. Sorry about picking up a rather ancient thread, but this didn't bite me until now (when I upgraded to 2.6.4); Wayne wrote: I've also checked in an improvement to safe_fname() that makes it use isprint() (instead of just looking for newlines). Is there a chance that this feature will become selectable? I have some scripts that rely on a specially formatted log (made with --log-format) to do some post-processing after (or during) the transfer, and these now fail, since several files (whose names contain non-ascii chars) might be squashed into the same string. Alternatively, how about escaping the chars instead of just munging them? I.e. output files like two-line\x0afile name or P\xe5ske (norwegian for easter, for the curious;), or something like that? Vidar -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: patch for replacing non-printable chars in filenames
Oops, I should have added that for isprint() (in safe_fname()) to be locale-aware at all, you need to add a call to setlocale(LC_CTYPE, ). Vidar -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
PATCH: rsyncd permission options
hello! 2.6.4 is out -- I'm too late again :-( I've posted an older version of this patch in the past and this time I hope it will make it into the source tree. Because loadparms.c and rsyncd.conf.yo have changed `make proto' and `make man' have to be called. rsyncd.conf options to handle file permissions (stolen from samba) This patch is made to provide more control on the permissions of files and directories that are uploaded to a rsyncd-server. Normally when files and directories are uploaded to a rsyncd they are created with the permissions of the source. Especially in the case that user and group are set to special values using the 'uid' and 'gid' directives it does not much sense to use the source permission pattern. There is a patch introducing a new chmod command line option but normally you may want to control the permissions on server side. The patch below will allow you to modify file and directory permissions by using 4 new rsyncd.conf directives. I'm sure that those 2 patches will not break each other and it really makes sense to use them both. You may know this options from samba. create mask When a file is created (or touched) by rsyncd the permissions will be taken from the source file bit-wise 'AND'ed with this parameter. This parameter may be thought of as a bit-wise MASK for the UNIX modes of a file. Any bit not set here will be removed from the modes set on a file when it is created. The default value of this parameter is set to 0 to be provide the default behaviour of older versions. Following this rsync will bit-wise 'OR' the UNIX mode created from this parameter with the value of the force create mode parameter which is set to 000 by default. This parameter does not affect directory modes. See the parameter directory mask for details. See also the force create mode parameter for forcing particular mode bits to be set on created files. See also the directory mask parameter for masking mode bits on created directories. Default: create mask = 0 Example: create mask = 0644 force create mode This parameter specifies a set of UNIX mode bit permissions that will always be set on a file created by rsyncd. This is done by bitwise 'OR'ing these bits onto the mode bits of a file that is being created or having its permissions changed. The default for this parameter is (in octal) 000. The modes in this parameter are bitwise 'OR'ed onto the file mode after the mask set in the create mask parameter is applied. See also the parameter create mask for details on masking mode bits on files. Default: force create mode = 000 Example: force create mode = 0644 directory mask When a directory is created (or touched) by rsyncd the permissions will be taken from the source directory bit-wise 'AND'ed with this parameter. This parameter may be thought of as a bit-wise MASK for the UNIX modes of a file. Any bit not set here will be removed from the modes set on a file when it is created. The default value of this parameter is set to 0 to be provide the default behaviour of older versions. Following this rsync will bit-wise 'OR' the UNIX mode created from this parameter with the value of the force directory mode parameter which is set to 000 by default. This parameter does not affect file modes. See the parameter create mask for details. See also the force directory mode parameter for forcing particular mode bits to be set on created directories. See also the create mask parameter for masking mode bits on created files. Default: directory mask = 0 Example: directory mask = 0755 force directory mode This parameter specifies a set of UNIX mode bit permissions that will always be set on a directory created by rsyncd. This is done by bitwise 'OR'ing these bits onto the mode bits of a directory that is being created. The default for this parameter is (in octal) which will not add any extra permission bits to a created directory. This operation is done after the mode mask in the parameter directory mask is applied. See also the parameter directory mask for details on masking mode bits on created directories. Default: force directory mode = 000 Example: force directory mode = 0755 cu, Stefan -- Stefan Nehlsen | ParlaNet Administration | [EMAIL PROTECTED] | +49 431 988-1260 diff -u rsync-2.6.4/loadparm.c rsync-2.6.4-rsyncd-perm/loadparm.c --- rsync-2.6.4/loadparm.c 2005-02-19 18:38:51.0 +0100 +++
Some files not logged when using --compare-dest. Bug?
Hi again. I just spotted another peculiarity when inspecting the rsync log. When using --compare-dest, source files that have permissions that differ from the comparables are not logged, unless you're using -i. Here's a testing session: $ ls -lR .: total 12 drwxr-xr-x 2 vidar users 4096 2005-03-31 14:16 cmp/ drwxr-xr-x 2 vidar users 4096 2005-03-31 14:23 dst/ drwxr-xr-x 2 vidar users 4096 2005-03-31 14:16 src/ ./cmp: total 4 -rwxr-xr-x 1 vidar users 17 2005-03-31 14:16 slackware-version* ./dst: total 0 ./src: total 4 -rw-r--r-- 1 vidar users 17 2005-03-31 14:16 slackware-version Note the permissions; the cmp file has been chmodded a+x. $ rsync -av --compare-dest=../cmp src/ dst/ building file list ... done ./ sent 115 bytes received 32 bytes 294.00 bytes/sec total size is 17 speedup is 0.12 $ ls -l dst total 4 -rw-r--r-- 1 vidar users 17 2005-03-31 14:16 slackware-version So the file was copied despite not being listed $ rm dst/slackware-version $ rsync -avi --compare-dest=../cmp src/ dst/ building file list ... done .d..t ./ .f...p... slackware-version sent 115 bytes received 32 bytes 294.00 bytes/sec total size is 17 speedup is 0.12 $ The same behaviour can be seen when using --log-format instead of -v; if there's an %i present, everything is logged correctly, but without, files with different permissions are silently left out. Vidar -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: patch for replacing non-printable chars in filenames
On Thu, Mar 31, 2005 at 01:17:16PM +0200, Vidar Madsen wrote:
Alternatively, how about escaping the chars instead of just munging
them? I.e. output files like two-line\x0afile name or P\xe5ske
(norwegian for easter, for the curious;), or something like that?
I'd be fine with that. It would mean doubling \ characters as well,
though. Anyone else have an opinion on this?
Appended is a patch that does the suggested escaping.
..wayne..
--- util.c 30 Mar 2005 19:34:20 - 1.181
+++ util.c 31 Mar 2005 16:09:16 -
@@ -877,11 +877,12 @@ int pop_dir(char *dir)
return 1;
}
-/* Return the filename, turning any non-printable characters into '?'s.
- * This ensures that outputting it on a line of its own cannot generate an
- * empty line. This function can return only MAX_SAFE_NAMES values at a
- * time! The returned value can be longer than MAXPATHLEN (because we
- * may be trying to output an error about a too-long filename)! */
+/* Return the filename, turning any non-printable characters into escaped
+ * characters (e.g. \n - \x0d, \ - \\). This ensures that outputting it
+ * cannot generate an empty line nor corrupt the screen. This function can
+ * return only MAX_SAFE_NAMES values at a time! The returned value can be
+ * longer than MAXPATHLEN (because we may be trying to output an error about
+ * a too-long filename)! */
char *safe_fname(const char *fname)
{
#define MAX_SAFE_NAMES 4
@@ -891,13 +892,21 @@ char *safe_fname(const char *fname)
char *t;
ndx = (ndx + 1) % MAX_SAFE_NAMES;
- for (t = fbuf[ndx]; *fname; fname++) {
- if (!isprint(*(uchar*)fname))
- *t++ = '?';
- else
+ for (t = fbuf[ndx]; *fname limit; fname++) {
+ if (*fname == '\\') {
+ if ((limit -= 2) 0)
+ break;
+ *t++ = '\\';
+ *t++ = '\\';
+ } else if (!isprint(*(uchar*)fname)) {
+ if ((limit -= 3) 0)
+ break;
+ sprintf(t, \\%02x, *(uchar*)fname);
+ t += 3;
+ } else {
+ limit--;
*t++ = *fname;
- if (--limit == 0)
- break;
+ }
}
*t = '\0';
--
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: files' timestamp handling - bug or design decision?
On Wed, Mar 30, 2005 at 09:16:03PM -0800, Eugene Kramer wrote: However, when the two are combined, the destination gets updated whenever the files in the source are touched. Just to be clear, the timestamp gets changed, though the file is not transferred due to the --checksum option (the --size-only option has no effect with --checksum). Rsync always brings the destination in sync with the source with whatever attributes you've told it to preserve, so what you're trying to do won't work. ..wayne.. -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: save on other directory
On Tue, Mar 29, 2005 at 06:39:50PM +0200, Alejandro Feij?o wrote: AFTER (cd /BACKUP and rsync -av --compare-dest=../FULL/ CLIENT:/ monday/) The --compare-dest directory is relative to the destination, so since FULL is not in the parent dir of monday, ../FULL is not the right way to refer to it. You should use --compare-dest=../../FULL instead (or just --compare-dest=/FULL, if appropriate). ..wayne.. -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
[Bug 2561] New: rsync crashes when using the exclude from option on server side.
https://bugzilla.samba.org/show_bug.cgi?id=2561
Summary: rsync crashes when using the exclude from option on
server side.
Product: rsync
Version: 2.6.4
Platform: x86
OS/Version: Linux
Status: NEW
Severity: major
Priority: P3
Component: core
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
QAContact: [EMAIL PROTECTED]
2.6.4 seems to have broken the exclude from option on server site. This is
the setup (works flawlessy with 2.6.3):
client call: 'rsync -a -K -H -e ssh -i /root/.ssh/rsync/id_dsa -l root --
delete --delete-excluded --force --numeric-ids'
ssh command on server: 'rsync --server --daemon --config=/root/rsync/conf .'
/root/rsync/conf contains:
==
log file = /var/log/rsyncd.log
pid file = /var/run/rsyncd.pid
use chroot = no
[rootfs]
path = /
max connections = 1
list = no
uid = root
include from = /root/rsync/include
exclude from = /root/rsync/exclude
hosts allow = IP,127.0.0.1
transfer logging = yes
refuse options = delete*
==
/root/rsync/include is empty (but does exist)
/root/rsync/exclude contains:
=
/jail/backup/*
/jail/ftpproxy/cache/0*
/jail/webproxy/cache/*
/media/*
/mnt/*
/parts/*
/proc/*
/sys/*
/tmp/*
/usr/src/linux-*-vanilla
/var/lib/YaST2/you/*
/var/run/*.pid
/var/run/rsyncd.lock
/var/spool/MailScanner/archive/*
/var/spool/MailScanner/incoming/*
/var/spool/MailScanner/quarantine/*
===
rsync crashes with following message:
rsync: connection unexpectedly closed (0 bytes received so far) [receiver]
rsync error: error in rsync protocol data stream (code 12) at io.c(420)
When I change the ssh command on the server to the following (strace is
added): 'strace rsync --server --daemon --config=/root/rsync/conf .', strace
logs this (last 10 lines):
===
open(/root/rsync/include, O_RDONLY|O_LARGEFILE) = 5
fstat64(5, {st_mode=S_IFREG|0600, st_size=0, ...}) = 0
mmap2(NULL, 131072, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xb7fb7000
read(5, , 131072) = 0
close(5)= 0
munmap(0xb7fb7000, 131072) = 0
open(/root/rsync/exclude, O_RDONLY|O_LARGEFILE) = 5
fstat64(5, {st_mode=S_IFREG|0600, st_size=294, ...}) = 0
mmap2(NULL, 131072, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xb7fb7000
read(5, /jail/backup/*\n/jail/ftpproxy/ca..., 131072) = 294
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV +++
=
When the exclude from option is commented out (or deleted)
in /root/rsync/conf, rsync works. However, rsync still crashes when only
entries in /root/rsync/exclude are commented out (with the exclude from
option in /root/rsync/conf in tact).
--
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.
--
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: files' timestamp handling - bug or design decision?
I want to be able to do two things together: -- transfer files from the source to destination only if the files' contents is changed rsync -avr Consider: -W -x --delete --delete-excluded --log-format='%i %f' Use --dry-run when testing for the right configuration to avoid data loose. -- when the files are transfered, I want to preserve original timestamp Try -a. By looking at the switches available in rsync, I assumed that a combination of --times and --checksum would do what I want, but apparently, --times not only tells rsync to preserve timestamps on transfer, but also to consider the files for the transfer if there is a discrepancy in the mtime of the files. rsync's defaults is pretty sane, and does what you want in most cases. Try rsync -avr --dry-run and see, if this doesn't solve your needs. -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
2.6.4 Potential protocol-corrupting bug
Hi all, I was just wondering if the following bugfix in 2.6.4 was a serious problem that could cause a problem in a destination file and if it did would that get picked up by the checksum ? Cheers - Steve - Fixed a potential protocol-corrupting bug where the generator could merge a message from the receiver into the middle of a multiplexed packet of data if only part of that data had been written out to the socket when the message from the generator arrived. -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
cwRsync 1.2.9 with rsync 2.6.4 is released !!
Hi, cwRsync version 1.2.9 is available for download at http://prdownloads.sourceforge.net/sereds/cwRsync_1.2.9_Installer.zip?downlo ad Rgrds _tev_ -- HIGHLIGHTS - Rsync 2.6.4 - Cygwin 1.5.13-1 Signatures: MD5: 1126808de99c67701aa74988ea83e7ec *cwRsync_1.2.9_Installer.zip SHA1: 6a2326716f7800521a72976f37f3b5b923037eff *cwRsync_1.2.9_Installer.zip - http://itefix.no/cwrsync http://sourceforge.net/projects/sereds -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: 2.6.4 Potential protocol-corrupting bug
On Thu, Mar 31, 2005 at 01:08:26PM -0800, Steve Harris wrote: I was just wondering if the following bugfix in 2.6.4 was a serious problem that could cause a problem in a destination file and if it did would that get picked up by the checksum ? The problem would have most likely caused the protocol to abort. If you're using 2.6.3, it should not have caused a corrupted destination file unless you had --partial enabled (which tells rsync to keep a corrupted file). However, older rsync versions used to save the failed-to-verify file in place of the destination file, so I suppose there's a chance that rsync could have lived long enough to tell the receiver to create a file with some bogus data and then died before the resend fixed it. ..wayne.. -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
[Bug 2561] rsync crashes when using the exclude from option on server side.
https://bugzilla.samba.org/show_bug.cgi?id=2561 --- Additional Comments From [EMAIL PROTECTED] 2005-03-31 17:18 --- Created an attachment (id=1129) -- (https://bugzilla.samba.org/attachment.cgi?id=1129action=view) Fix crash when module-path is / and excludes are anchored. This patch should be the correct fix for this bug when chroot is disabled. -- 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. -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Is rsync right for us?
Do I have to tell rsync what the username and password is for the remote IBM? Yes, one way or the other. Append -e ssh -l root or if you have an identity key, so you won't have to type password (this is copy/paste from a previous bug repport) -e ssh -i /root/.ssh/rsync/id_dsa -l root Are you running a rsync server on the IBM? In case you aren't you can try this (again copy/paste) rsync --server --daemon --config=/root/rsync/conf . /root/rsync/conf contains: == log file = /var/log/rsyncd.log pid file = /var/run/rsyncd.pid use chroot = no [rootfs] path = / max connections = 1 list = no uid = root include from = /root/rsync/include exclude from = /root/rsync/exclude hosts allow = IP,127.0.0.1 transfer logging = yes refuse options = delete* == Remove the double dashed lines (the equal signs) and replace IP with the client (your case G4) IP. -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: patch for replacing non-printable chars in filenames
On Thu, Mar 31, 2005 at 08:13:52AM -0800, Wayne Davison wrote: Appended is a patch that does the suggested escaping. Actually, that patch didn't put the suggested 'x' in after the '\'. After trying this a bit, I now think it would read better to use 3-digit octal escaping. That would turn a \n into \012 instead of \x0a, for instance. The changes to the prior patch are as easy as increasing the '3's to '4's, changing the sprintf() format to \\%03o, and fixing the function comment. ..wayne.. -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
CVS update: rsync
Date: Thu Mar 31 23:30:03 2005 Author: wayned Update of /data/cvs/rsync In directory dp.samba.org:/tmp/cvs-serv2 Modified Files: generator.c Log Message: Don't try to tweak read-only dest-dir permissions in list-only mode. Revisions: generator.c 1.194 = 1.195 http://www.samba.org/cgi-bin/cvsweb/rsync/generator.c?r1=1.194r2=1.195 ___ rsync-cvs mailing list rsync-cvs@lists.samba.org https://lists.samba.org/mailman/listinfo/rsync-cvs
