similar to: Clarification on the RSYNC_RAW_STATUS and RSYNC_EXIT_STATUS

I'm guessing no one else has seen this issue? Most exit codes are properly reported (e.g. code 12, code 10, code 2). The specific scenario is when a filename too long or directory not present error causes the client to exit with a code of 23 (reported as the exit code on the client properly and captured in the environment variable there). The exit code of the server still shows an exit code

https://bugzilla.samba.org/show_bug.cgi?id=3778 Summary: rsync triggers ( pre/post xter scripts ) Product: rsync Version: 2.6.8 Platform: Sparc OS/Version: Windows XP Status: NEW Severity: major Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy:

Hello Regarding ownership on the destination: rsync's man page indicates that when synchronizing files to a remote host, -o implies the --numeric-ids option, which makes perfect sense aince the named users/groups may not exist on the destination host. The problem I have is that the files created on the destination still appear to be owned by the local user (server1) on the rsync

I've got a patch that changes f_name_to() to return an unsigned int (like snprintf() and strlcpy() do) and adds checking to ensure that we didn't overflow the name before we try to use it: http://www.blorf.net/name-overflow.patch If anyone would care to check out the following patch before I commit it, please do. ..wayne..

I've been working on an update to my --files-from patch that I think will soon be ready to be committed to CVS. See if you agree. For those that have been following the saga, here's a list of just the changes since the last patch (for those that haven't, see the next section): Changes Since the Last Release: =============================== - The --null option was renamed to

When I was working on the the hard-link change, I noticed that many of the hard-link verbose messages were getting lost. These messages get output very near the end of the transfer, and it turns out that the reason for the loss was that there are two pipes flowing from the generator and the receiver, and it was possible for the "we're all done" message to get received down the redo

I've been running some tests on files created by rsync and noticing fragmentation issues. I started the testing because our 5TB array started performing very slowly and it appears fragmentation was the culprit. The test I conducted was straighforward: 1. Copy over a 49GB file. Analyzed with contig (from sysinternals), no fragments. 2. Ran rsync and the file was recreated normally (rsync

As threatened a while back, there are some exclude/include bugs that I'd like to see fixed in rsync. Here is the patch: http://www.blorf.net/rsync-exclude.patch This fixes the following bugs: - A non-anchored, slash-including pattern with a wildcard needs to be matched at the end of the path (e.g. "CVS/R* should match throughout the tree, not just at /CVS/R*). - A leading

I've released rsync 2.6.0pre2. This should be the final pre-release before 2.6.0 goes final (which is scheduled to happen on January 1st). If you'd like to assist in making the final release smoother, please try this out and let me know if you encounter any problems: http://samba.org/ftp/rsync/preview/rsync-2.6.0pre2.tar.gz http://samba.org/ftp/rsync/preview/rsync-2.6.0pre2.tar.gz.sig

I've released rsync 2.6.0pre2. This should be the final pre-release before 2.6.0 goes final (which is scheduled to happen on January 1st). If you'd like to assist in making the final release smoother, please try this out and let me know if you encounter any problems: http://samba.org/ftp/rsync/preview/rsync-2.6.0pre2.tar.gz http://samba.org/ftp/rsync/preview/rsync-2.6.0pre2.tar.gz.sig

I know this has been discussed repeatedly, so might even say beaten to death, but it is a feature which I need to use. I notice Wayne had a patch to do this listed in the list archives, but I don't know what version of rsync he was patching against. What is the general opinion on using this patch for reliable rsync'ing of extremely small volumes of data of high cost, high latency comms

Hi, My name is Vu Huynh. I'm currently work for Atmel Corporation. We're using Rsync v2.5.7 to rsync design kits between our remote sites. It works fine for all small kit directories. However, there is 1 BIG kit directory (But there is no file has the size of bigger than 100MB) that always gets "rsync: connection unexpectedly closed" Error. The Full Error Message

I have been trying for quite a while now to understand why is the flist.c:f_name() function implemented using static buffers. Anyone care to comment? The immediate problem is that any call to f_name overrides the previous content (well, obvious). This, combined with the fact that several function calls are made with the result of f_name(file) results in problems handling hardlinks - and

rsync version 2.6.9cvs protocol version 29 Running rsync from an rsnapshot script I get the following error: unknown message 4:1 [generator] rsync error: error in rsync protocol data stream (code 12) at io.c(307) [generator=2.6.9cvs] rsync: connection unexpectedly closed (1718 bytes received so far) [sender] rsync error: error in rsync protocol data stream (code 12) at io.c(453)

People who follow Samba development may have noticed the following commit that just went into the Samba repo: https://git.samba.org/?p=samba.git;a=blob;f=VFS-License-clarification.txt;h=6b67381cc20412456d7d01a0587c0d627254a2b8;hb=1262b13f4db9502c36579b7dd740d8002e0baac9 For people who don't read git (I'm assuming that's everyone :-) it's a clarification around GPL license

Hi, Just seeking some clarification on the current state of play with masqing ipsec connections. I have a client who establishs many different outbound ipsec connections. So thats - many local clients, through linux firewall, to many different ipsec ''servers''. they currently assign a public ip for outbound nat to each user to connect out to the ipsec connection, so we have a one

Dear All, Currently working setup is CentOS4.4 Linux I tried to google-out, but i can't able to findout I need some clarification about CD writer support 1. How can i findout inserted disc is CD or DVD from command line 2. How can i findout inserted disc is empty from command line 3. How can i findout inserted disc size (like 700 MB or 4.7 GB) from command line

https://bugzilla.mindrot.org/show_bug.cgi?id=2262 Bug ID: 2262 Summary: Clarification for the usage of Match directives with negations Product: Portable OpenSSH Version: 6.6p1 Hardware: Other OS: All Status: NEW Severity: enhancement Priority: P5 Component:

Hi, I am considering implementing the Ogg bitstream spec. Having read the spec, I am left with just one matter requiring clarification (making it a pretty well written spec, in my book): Can a packet begin on the same page as the previous packet ends on? The spec does not appear to be explicit about this. It would seem that I could indicate that there were (e.g.) 3 segments in my page,

Good afternoon, As a clarification does it make sense to remove the second 'not' in the 'See Also' documentation for file_test ? Kind regards, Sean O'Riordain ----- Index: src/library/utils/man/filetest.Rd =================================================================== --- src/library/utils/man/filetest.Rd (revision 55639) +++ src/library/utils/man/filetest.Rd