Re: rsync error: protocol incompatibility (code 2) at main.c(451)
On Tue, Mar 15, 2005 at 06:54:16AM +0100, Dag Wieers wrote: Another update. Only some of the hardlinks seem to be actually missing. Does this make any sense ? Yes, that gives me something to go on for testing. I should hopefully be able to reproduce what is going on. ..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: rsync error: protocol incompatibility (code 2) at main.c(451)
On Tue, Mar 15, 2005 at 04:15:46AM +0100, Dag Wieers wrote: Invalid packet at end of run [sender] OK, this was a combination of --delay-updates and --hard-links that was causing a problem at the end of the run. I've checked in a fix to CVS, and the latest nightly tar file has this fix present. I'm confident that will take care of the problem for you. Thanks for the help! ..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: rsync error: protocol incompatibility (code 2) at main.c(451)
On Tue, 15 Mar 2005, Wayne Davison wrote: On Tue, Mar 15, 2005 at 04:15:46AM +0100, Dag Wieers wrote: Invalid packet at end of run [sender] OK, this was a combination of --delay-updates and --hard-links that was causing a problem at the end of the run. I've checked in a fix to CVS, and the latest nightly tar file has this fix present. I'm confident that will take care of the problem for you. Thanks for the help! Great service. :) I will package rsync-HEAD-20050315-1733GMT and send some feedback. Thanks ! -- dag wieers, [EMAIL PROTECTED], http://dag.wieers.com/ -- [all I want is a warm bed and a kind word and unlimited power] -- 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: rsync error: protocol incompatibility (code 2) at main.c(451)
Dunno if this has any relationship (or even if this is the right place to break in) SERVER: rsync-HEAD-20050314-2227GMT rsync error: protocol incompatibility (code 2) at io.c(915) rsync error: protocol incompatibility (code 2) at sender.c(157) CLIENT: rsync version 2.6.3 protocol version 29 Server upgraded from VERY OLD 2.4.1-2 (rpm) to latest (bugsall) Server to current version 2.6.3 and everything is fine, as far as I am concerned. I have the latest on a very sacrificial clone of the SERVER and can duplicate the errors. Mar 15 10:21:46 2bizbox rsyncd[24957]: rsyncd version 2.6.4pre2 starting, listening on port 873 Mar 15 10:21:46 2bizbox modprobe: modprobe: Can't locate module net-pf-10 Mar 15 10:50:52 2bizbox rsyncd[1204]: rsyncd version 2.6.3 starting, listening on port 873 Mar 15 10:50:52 2bizbox modprobe: modprobe: Can't locate module net-pf-10 The above is from the server. The clone is sufficiently messed up that most everything is disabled. Better to make mistakes where the consequences are irrelevant. If this is relevant or if I can help with it, please let me know. I've been around awhile, but it's safer to assume that I'm a very green newbie. (You guys are too fast) CLONE: rsync-HEAD-20050315-1733GMT] [EMAIL PROTECTED] local]# rsync -avPLz --password-file=/etc/rsync/rsync.2bb [EMAIL PROTECTED]::mysql-2bb/srv/b* /tmp/ receiving file list ... 6 files to consider bm.MYD Invalid file index: 65536 (count=6) [sender] rsync error: protocol incompatibility (code 2) at sender.c(157) rsync: connection unexpectedly closed (139 bytes received so far) [receiver] rsync error: error in rsync protocol data stream (code 12) at io.c(363) rsync: connection unexpectedly closed (123 bytes received so far) [generator] rsync error: error in rsync protocol data stream (code 12) at io.c(363) Different place in io.c (but different test from different server) Same result going back to rsync-HEAD-20050314-2227GMT on clone. Actually I'm impressed. I like things that do little to no damage when broken. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Wayne Davison Sent: Tuesday, March 15, 2005 11:37 AM To: Dag Wieers Cc: rsync@lists.samba.org Subject: Re: rsync error: protocol incompatibility (code 2) at main.c(451) On Tue, Mar 15, 2005 at 04:15:46AM +0100, Dag Wieers wrote: Invalid packet at end of run [sender] OK, this was a combination of --delay-updates and --hard-links that was causing a problem at the end of the run. I've checked in a fix to CVS, and the latest nightly tar file has this fix present. I'm confident that will take care of the problem for you. Thanks for the help! ..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 -- 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: rsync error: protocol incompatibility (code 2) at main.c(451)
On Tue, Mar 15, 2005 at 12:39:54PM -0600, [EMAIL PROTECTED] wrote: Dunno if this has any relationship (or even if this is the right place to break in) Seems like a decent place to jump in to me... Welcome! SERVER: rsync-HEAD-20050314-2227GMT rsync error: protocol incompatibility (code 2) at io.c(915) rsync error: protocol incompatibility (code 2) at sender.c(157) CLIENT: rsync version 2.6.3 protocol version 29 That 2.6.3 version is really a CVS version of the work that went into 2.6.4 from before it was being properly labelled as 2.6.4cvs (the give-away is that the protocol-version says 29, and 2.6.3 only supports up to 28). So, this error is actually expected due to some earlier changes to the protocol that happened before the pre-releases started. Your options are: upgrade the client to the same version of prerelease 2.6.4 as the server, downgrade the client to the real 2.6.3 release, or just add the option --protocol=28 and the two rsyncs will communicate via the older protocol that they both have in common. ..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 2455] New: rsync --daemon segfaults if log file = file dir does not exist
https://bugzilla.samba.org/show_bug.cgi?id=2455
Summary: rsync --daemon segfaults if log file = file dir does
not exist
Product: rsync
Version: 2.6.3
Platform: Sparc
OS/Version: Solaris
Status: NEW
Severity: normal
Priority: P3
Component: core
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
QAContact: [EMAIL PROTECTED]
# ./rsync --version
rsync version 2.6.2 protocol version 28
[etc. ... same bug with 2.6.3 and others]
# ./rsync --daemon --no-detach
Segmentation Fault(coredump)
# grep log /etc/rsyncd.conf
log file = /var/rsyncd/rsyncd.log
syslog facility = daemon
# ls -l /var/rsyncd
/var/rsyncd: No such file or directory
# mkdir /var/rsyncd
# ./rsync --daemon --no-detach
(runs great)
This was mystifying and required truss and/or gdb to figure out.
I added some code for a new category of error, a printed error message and a
proper error-exit. Here is the context diff of the changes; I hope this is
helpful:
Common subdirectories: rsync-2.6.3/doc and rsync-2.6.3_jdb/doc
diff -c rsync-2.6.3/errcode.h rsync-2.6.3_jdb/errcode.h
*** rsync-2.6.3/errcode.h Mon Dec 15 08:04:14 2003
--- rsync-2.6.3_jdb/errcode.h Tue Mar 15 19:36:28 2005
***
*** 42,48
#define RERR_VANISHED 24 /* file(s) vanished on sender side */
#define RERR_TIMEOUT30 /* timeout in data send/receive */
!
/* Although it doesn't seem to be specified anywhere,
* ssh and the shell seem to return these values:
*
--- 42,49
#define RERR_VANISHED 24 /* file(s) vanished on sender side */
#define RERR_TIMEOUT30 /* timeout in data send/receive */
! #define RERR_LOG_NOTOPENED 31 /* logfile could not be opened for appending
*/
!
/* Although it doesn't seem to be specified anywhere,
* ssh and the shell seem to return these values:
*
Common subdirectories: rsync-2.6.3/lib and rsync-2.6.3_jdb/lib
diff -c rsync-2.6.3/log.c rsync-2.6.3_jdb/log.c
*** rsync-2.6.3/log.c Sun Sep 5 21:30:00 2004
--- rsync-2.6.3_jdb/log.c Tue Mar 15 19:47:19 2005
***
*** 63,68
--- 63,69
{ RERR_PARTIAL, some files could not be transferred },
{ RERR_VANISHED , some files vanished before they could be
transferred },
{ RERR_TIMEOUT, timeout in data send/receive },
+ { RERR_LOG_NOTOPENED, log file could not be opened },
{ RERR_CMD_FAILED , remote shell failed },
{ RERR_CMD_KILLED , remote shell killed },
{ RERR_CMD_RUN, remote command could not be run },
***
*** 89,96
static void logit(int priority, char *buf)
{
if (logfname) {
! if (!logfile)
log_open();
fprintf(logfile,%s [%d] %s,
timestring(time(NULL)), (int)getpid(), buf);
fflush(logfile);
--- 90,103
static void logit(int priority, char *buf)
{
if (logfname) {
! if (!logfile) /* Try opening log file for appending */
log_open();
+
+ if (!logfile) { /* log file is still not open for some reason
*/
+ printf(ERROR: log file %s cannot be opened for
append\n, logfname);
+ exit_cleanup(RERR_LOG_NOTOPENED);
+ }
+
fprintf(logfile,%s [%d] %s,
timestring(time(NULL)), (int)getpid(), buf);
fflush(logfile);
Common subdirectories: rsync-2.6.3/packaging and rsync-2.6.3_jdb/packaging
Common subdirectories: rsync-2.6.3/patches and rsync-2.6.3_jdb/patches
Common subdirectories: rsync-2.6.3/popt and rsync-2.6.3_jdb/popt
diff -c rsync-2.6.3/rsync.yo rsync-2.6.3_jdb/rsync.yo
*** rsync-2.6.3/rsync.yoThu Sep 30 16:35:56 2004
--- rsync-2.6.3_jdb/rsync.yoTue Mar 15 19:36:23 2005
***
*** 1389,1394
--- 1389,1395
dit(bf(23)) Partial transfer due to error
dit(bf(24)) Partial transfer due to vanished source files
dit(bf(30)) Timeout in data send/receive
+ dit(bf(31)) Log file could not be opened for appending
enddit()
manpagesection(ENVIRONMENT VARIABLES)
Common subdirectories: rsync-2.6.3/testhelp and rsync-2.6.3_jdb/testhelp
Common subdirectories: rsync-2.6.3/testsuite and rsync-2.6.3_jdb/testsuite
Common subdirectories: rsync-2.6.3/zlib and rsync-2.6.3_jdb/zlib
--
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: include/exclude client/server precedence
ok, wayne: thank you a lot, next question in another thread now im using: include = [oO][uU][tT][lL][oO][oO][kK].[pP][sS][tT] [aA][lL][mM][aA][cC][eE][nN].[pP][sS][tT] exclude = *.[pP][iI][fF] *.[iI][sS][oO] *.[mM][oO][vV] *.[mM][pP][33] *.[wW][aA][vV] *.[eE][xX][eE] *.[dD][lL][lL] *.[pP][sS][tT] *.[cC][oO][mM] *.[bB][aA][tT] *.[mM][pP][gG] /Escritorio/publico/ Escritorio/personal/ in the global section of rsyncd.conf and works very well carlos #rsync.conf [module] include = outlook.pst exclude = *.pst *.exe *.com *.mp3 etc... but as i have experienced, these rules only apply if are repeated as client options They apply to the server, but not in the same way that client options do (i.e. they have no effect whatsoever on the client, just the server). This is mentioned in the rsyncd.conf (especiallly in a more modern release). The purpose of these options for the daemon is to completely hide files so that they can't be downloaded from the server, and to prevent those files from uploaded to the server (in a modern rsync). For 2.6.4, you can instead create a server-file named .rsync-filter in the root dir of the module. Then, the client can specify -F and these filter rules will be read-in during the processing. When pulling, if --delete-after is specified, the most recent version of the rules will be applied to protect files from deletion (or the previous version of the file will apply if another form of delete is used). When pushing, the client needs to have an up-to-date version of the file to prevent the transfer of those files to the server. ..wayne.. _ Express yourself instantly with MSN Messenger! Download today it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/ -- 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 2455] rsync --daemon segfaults if log file = file dir does not exist
https://bugzilla.samba.org/show_bug.cgi?id=2455 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2005-03-15 16:25 --- This has been fixed in CVS for a while now, and is mentioned in the NEWS file for the two pre-release versions of 2.6.4. I did notice that I failed to add a new error-code for this situation, so I have checked in a change to implement that. Thanks. -- 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: [rsync-announce] Rsync 2.6.4pre3 released (Out of Office)
I am out of the office Wednesday March 16th through Friday March 18th. Will return on Monday, March 21st. Thanks. -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Rsync 2.6.4pre3 released
I've released rsync 2.6.4pre3. I'm hoping that this will be pretty close to the final version for 2.6.4, so please beat on this and let me know if anything weird turns up! IMPORTANT: protocol 29 was revised in pre3 to be incompatible with pre1 and pre2, so be sure to update all your pre-release versions at the same time. Rsync has code in it to detect that it is talking to an older pre-release, so you should see an appropriate error if you try to mix incompatible versions. If upgrading the older pre-release version is not possible, use the --protocol=28 option to make the programs fall- back to a protocol they have in common (this is suggested in the error message that is output). All the changes since 2.6.3 are here: http://rsync.samba.org/ftp/rsync/preview/rsync-2.6.4pre2-NEWS The changes since 2.6.4pre2 are as follows: - Some protocol changes were made: (1) simplified the data flow for the generator's reporting of its basis-file choice to the receiver (because simplified data flow makes deadlock prevention easier); (2) made hard-linking be reported via the itemized log output; and (3) added an extra phase at the end of the transfer for the --delay-updates processing so that it can itemize any delayed hard-links. (These changes make protocol 29 incompatible with earlier pre-releases, as mentioned in the Important note above.) - Another change for hard-links: a cluster of hard-linked files is now dealt with as soon as possible, either when we complete the update of one file in the cluster, or we find an unchanged file in the cluster (the old code used to do all hard-linking at the end of the transfer). - When --max-delete=N is specified and we attempted to overflow this value, we now warn at the end of the transfer and exit with error code 25. If you want to know about too-many deletions prior to doing any deletes, do a check run with --dry-run first. - Fixed a potential protocol-corrupting bug in the data sent from the generator to the receiver (this doesn't seem to have been easy to trigger, though). - Fixed a slowdown in the name-sorting code. - When '%i' outputs a deletion, it uses the string *deleting (with the leading '*' being new). Also a few other minor changes to the itemized output, including adding an extra character for future code to be able to report when an ACL/extended-attribute changes. (See the man page for full details.) - Fixed a glitch in the --progress output when transferring zero- length files. - Fixed the over-reporting of changes to a write-protected directory. - The --copy-dest option has made a comeback into CVS now that its algorithm has been improved to work just like a --link-dest with copies instead of hard links (an earlier version of the code did a less efficient transfer of unchanged files from the --copy-dest hierarchy). You can grab the tar file and its signature here: http://rsync.samba.org/ftp/rsync/preview/rsync-2.6.4pre3.tar.gz http://rsync.samba.org/ftp/rsync/preview/rsync-2.6.4pre3.tar.gz.asc Please give it a try and send feedback! Thanks! ..wayne.. signature.asc Description: Digital signature -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Problem with rsync --inplace very slow/hung on large files
I'm trying to rsync a very large (62gig) file from one machine to another as part of a nightly backup. If the file does not exist at the destination, it takes about 2.5 hours to copy in my environment. But, if the file does exist and --inplace is specified, and the file contents differ, rsync either is so significantly slowed as to take more than 30 hours (the longest I've let an instance run), or it is just hung. Running with -vvv gives this as the last few lines of the output: match at 205401064 last_match=205401064 j=821 len=250184 n=0 match at 205651248 last_match=205651248 j=822 len=250184 n=0 match at 205901432 last_match=205901432 j=823 len=250184 n=0 match at 206151616 last_match=206151616 j=824 len=250184 n=0 at which point it has not printed anything else since I last looked at the current run attempt about 8 hours ago. Doing an strace on the rsync processes on the sending and receiving machines it appears that there is still reading and writing going on, but there isn't any output from the -vvv and I can't tell if it's really doing anything. Is this excessive slowness just an artifact of doing an rsync --inplace on such a large file, and it will eventually complete if let run long enough? I would try testing without the --inplace, but the system in question doesn't have enough disk space for two copies of that size file, which is why I am using --inplace. Using 2.6.3, on Debian. Any help appreciated. Evan -- 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: Tue Mar 15 17:30:50 2005 Author: wayned Update of /data/cvs/rsync In directory dp.samba.org:/tmp/cvs-serv21985 Modified Files: main.c Log Message: Mention the index number for an invalid packet at end of run. Revisions: main.c 1.265 = 1.266 http://www.samba.org/cgi-bin/cvsweb/rsync/main.c?r1=1.265r2=1.266 ___ rsync-cvs mailing list rsync-cvs@lists.samba.org https://lists.samba.org/mailman/listinfo/rsync-cvs
CVS update: rsync
Date: Tue Mar 15 17:30:53 2005 Author: wayned Update of /data/cvs/rsync In directory dp.samba.org:/tmp/cvs-serv22048 Modified Files: receiver.c Log Message: Handle --delay-updates at the end of the first phase. Revisions: receiver.c 1.154 = 1.155 http://www.samba.org/cgi-bin/cvsweb/rsync/receiver.c?r1=1.154r2=1.155 ___ rsync-cvs mailing list rsync-cvs@lists.samba.org https://lists.samba.org/mailman/listinfo/rsync-cvs
CVS update: rsync
Date: Tue Mar 15 19:19:36 2005 Author: wayned Update of /data/cvs/rsync In directory dp.samba.org:/tmp/cvs-serv20687 Modified Files: rsync.h Log Message: Added ITEM_DUMMY_BIT and moved a few other 'ITEM_*'s around. Revisions: rsync.h 1.258 = 1.259 http://www.samba.org/cgi-bin/cvsweb/rsync/rsync.h?r1=1.258r2=1.259 ___ rsync-cvs mailing list rsync-cvs@lists.samba.org https://lists.samba.org/mailman/listinfo/rsync-cvs
CVS update: rsync
Date: Tue Mar 15 19:19:41 2005 Author: wayned Update of /data/cvs/rsync In directory dp.samba.org:/tmp/cvs-serv20720 Modified Files: receiver.c Log Message: Added an extra phase to the end of the transfer to handle delayed updates that have hard links. Revisions: receiver.c 1.155 = 1.156 http://www.samba.org/cgi-bin/cvsweb/rsync/receiver.c?r1=1.155r2=1.156 ___ rsync-cvs mailing list rsync-cvs@lists.samba.org https://lists.samba.org/mailman/listinfo/rsync-cvs
CVS update: rsync
Date: Tue Mar 15 19:19:44 2005 Author: wayned Update of /data/cvs/rsync In directory dp.samba.org:/tmp/cvs-serv20737 Modified Files: sender.c Log Message: - Made read_item_attrs() detect and reject a pre1/pre2 rsync (used by both the sender and the receiver). - Added an extra phase to the end of the transfer to better handle delayed updates that have hard links. Revisions: sender.c1.82 = 1.83 http://www.samba.org/cgi-bin/cvsweb/rsync/sender.c?r1=1.82r2=1.83 ___ rsync-cvs mailing list rsync-cvs@lists.samba.org https://lists.samba.org/mailman/listinfo/rsync-cvs
CVS update: rsync
Date: Tue Mar 15 23:23:39 2005 Author: wayned Update of /data/cvs/rsync In directory dp.samba.org:/tmp/cvs-serv22805 Modified Files: errcode.h Log Message: Added RERR_LOG_FAILURE define. Revisions: errcode.h 1.9 = 1.10 http://www.samba.org/cgi-bin/cvsweb/rsync/errcode.h?r1=1.9r2=1.10 ___ rsync-cvs mailing list rsync-cvs@lists.samba.org https://lists.samba.org/mailman/listinfo/rsync-cvs
CVS update: rsync
Date: Tue Mar 15 23:23:41 2005 Author: wayned Update of /data/cvs/rsync In directory dp.samba.org:/tmp/cvs-serv23137 Modified Files: log.c Log Message: Added the error message for RERR_LOG_FAILURE and used it when the daemon can't open the log-file. Revisions: log.c 1.99 = 1.100 http://www.samba.org/cgi-bin/cvsweb/rsync/log.c?r1=1.99r2=1.100 ___ rsync-cvs mailing list rsync-cvs@lists.samba.org https://lists.samba.org/mailman/listinfo/rsync-cvs
CVS update: rsync
Date: Tue Mar 15 23:23:45 2005 Author: wayned Update of /data/cvs/rsync In directory dp.samba.org:/tmp/cvs-serv23384 Modified Files: rsync.yo rsync.1 Log Message: Document error messages 6 and 25. Revisions: rsync.yo1.263 = 1.264 http://www.samba.org/cgi-bin/cvsweb/rsync/rsync.yo?r1=1.263r2=1.264 rsync.1 1.275 = 1.276 http://www.samba.org/cgi-bin/cvsweb/rsync/rsync.1?r1=1.275r2=1.276 ___ rsync-cvs mailing list rsync-cvs@lists.samba.org https://lists.samba.org/mailman/listinfo/rsync-cvs
CVS update: rsync/patches
Date: Wed Mar 16 02:26:44 2005 Author: wayned Update of /data/cvs/rsync/patches In directory dp.samba.org:/tmp/cvs-serv7635 Modified Files: acls.diff append.diff Log Message: Fixed failing hunks. Revisions: acls.diff 1.42 = 1.43 http://www.samba.org/cgi-bin/cvsweb/rsync/patches/acls.diff?r1=1.42r2=1.43 append.diff 1.15 = 1.16 http://www.samba.org/cgi-bin/cvsweb/rsync/patches/append.diff?r1=1.15r2=1.16 ___ rsync-cvs mailing list rsync-cvs@lists.samba.org https://lists.samba.org/mailman/listinfo/rsync-cvs
CVS update: rsync/patches
Date: Wed Mar 16 02:28:30 2005 Author: wayned Update of /data/cvs/rsync/patches In directory dp.samba.org:/tmp/cvs-serv7795 Modified Files: ODBC-dblog.diff backup-dir-dels.diff chmod-option.diff copy-atimes.diff date-only.diff fname-convert.diff fsync.diff ignore-case.diff last-match.diff link-by-hash.diff links-depth.diff netgroup-auth.diff openssl-support.diff owner-group-mod.diff soften-links.diff source-cd.diff time-limit.diff tru64.diff Log Message: Updated to apply cleanly. Revisions: ODBC-dblog.diff 1.29 = 1.30 http://www.samba.org/cgi-bin/cvsweb/rsync/patches/ODBC-dblog.diff?r1=1.29r2=1.30 backup-dir-dels.diff1.34 = 1.35 http://www.samba.org/cgi-bin/cvsweb/rsync/patches/backup-dir-dels.diff?r1=1.34r2=1.35 chmod-option.diff 1.39 = 1.40 http://www.samba.org/cgi-bin/cvsweb/rsync/patches/chmod-option.diff?r1=1.39r2=1.40 copy-atimes.diff1.43 = 1.44 http://www.samba.org/cgi-bin/cvsweb/rsync/patches/copy-atimes.diff?r1=1.43r2=1.44 date-only.diff 1.30 = 1.31 http://www.samba.org/cgi-bin/cvsweb/rsync/patches/date-only.diff?r1=1.30r2=1.31 fname-convert.diff 1.43 = 1.44 http://www.samba.org/cgi-bin/cvsweb/rsync/patches/fname-convert.diff?r1=1.43r2=1.44 fsync.diff 1.29 = 1.30 http://www.samba.org/cgi-bin/cvsweb/rsync/patches/fsync.diff?r1=1.29r2=1.30 ignore-case.diff1.29 = 1.30 http://www.samba.org/cgi-bin/cvsweb/rsync/patches/ignore-case.diff?r1=1.29r2=1.30 last-match.diff 1.2 = 1.3 http://www.samba.org/cgi-bin/cvsweb/rsync/patches/last-match.diff?r1=1.2r2=1.3 link-by-hash.diff 1.49 = 1.50 http://www.samba.org/cgi-bin/cvsweb/rsync/patches/link-by-hash.diff?r1=1.49r2=1.50 links-depth.diff1.19 = 1.20 http://www.samba.org/cgi-bin/cvsweb/rsync/patches/links-depth.diff?r1=1.19r2=1.20 netgroup-auth.diff 1.6 = 1.7 http://www.samba.org/cgi-bin/cvsweb/rsync/patches/netgroup-auth.diff?r1=1.6r2=1.7 openssl-support.diff1.37 = 1.38 http://www.samba.org/cgi-bin/cvsweb/rsync/patches/openssl-support.diff?r1=1.37r2=1.38 owner-group-mod.diff1.16 = 1.17 http://www.samba.org/cgi-bin/cvsweb/rsync/patches/owner-group-mod.diff?r1=1.16r2=1.17 soften-links.diff 1.7 = 1.8 http://www.samba.org/cgi-bin/cvsweb/rsync/patches/soften-links.diff?r1=1.7r2=1.8 source-cd.diff 1.8 = 1.9 http://www.samba.org/cgi-bin/cvsweb/rsync/patches/source-cd.diff?r1=1.8r2=1.9 time-limit.diff 1.41 = 1.42 http://www.samba.org/cgi-bin/cvsweb/rsync/patches/time-limit.diff?r1=1.41r2=1.42 tru64.diff 1.13 = 1.14 http://www.samba.org/cgi-bin/cvsweb/rsync/patches/tru64.diff?r1=1.13r2=1.14 ___ rsync-cvs mailing list rsync-cvs@lists.samba.org https://lists.samba.org/mailman/listinfo/rsync-cvs
CVS update: rsync
Date: Wed Mar 16 02:50:00 2005 Author: wayned Update of /data/cvs/rsync In directory dp.samba.org:/tmp/cvs-serv12617 Modified Files: NEWS Log Message: Mention one other recent change. Revisions: NEWS1.268 = 1.269 http://www.samba.org/cgi-bin/cvsweb/rsync/NEWS?r1=1.268r2=1.269 ___ rsync-cvs mailing list rsync-cvs@lists.samba.org https://lists.samba.org/mailman/listinfo/rsync-cvs
CVS update: rsyncweb
Date: Wed Mar 16 02:56:56 2005 Author: wayned Update of /data/cvs/rsyncweb In directory dp.samba.org:/tmp/cvs-serv14604 Modified Files: index.html Log Message: Mentioned the rsync-2.6.4pre3 release. Revisions: index.html 1.41 = 1.42 http://www.samba.org/cgi-bin/cvsweb/rsyncweb/index.html?r1=1.41r2=1.42 ___ rsync-cvs mailing list rsync-cvs@lists.samba.org https://lists.samba.org/mailman/listinfo/rsync-cvs
