[Bug 12386] Copy Loop

2016-10-20 Thread samba-bugs
https://bugzilla.samba.org/show_bug.cgi?id=12386 --- Comment #1 from Kevin Korb --- That isn't a bug you are using it wrong. drop the .* and it will do what you expect. There should almost never be a * in the source parameter. Also, don't rsync without --times unless you have a really good rea

[Bug 12386] New: Copy Loop

2016-10-20 Thread samba-bugs
https://bugzilla.samba.org/show_bug.cgi?id=12386 Bug ID: 12386 Summary: Copy Loop Product: rsync Version: 3.1.3 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 Component:

Re: -e escape rule

2016-10-20 Thread Samuel Williams
Hmm, so after reviewing this in a bit more detail.. it would be very nice if at least backslash escapes would be supported. Quoted strings are pretty ugly, especially when nested several levels. Anyway, just my 2 cents. -- Please use reply-all for most replies to avoid omitting the mailing list.

Re: -e escape rule

2016-10-20 Thread Samuel Williams
Hi Dave, thanks for point that out. I didn't realise there was a detailed explanation of that field in the man page, I only saw the summary. Yes, that clearly explains how it's supposed to work. On 21 October 2016 at 01:46, Dave Howorth wrote: > On 2016-10-20 10:24, Samuel Williams wrote: >> >> H

Re: rsync: connection unexpectedly closed

2016-10-20 Thread Bernd Hohmann
On 20.10.2016 03:24, Kip Warner wrote: > I ended up giving up. Me too. I'm copying all files via 'scp' now - takes 3 days but no aborts or errors. So I am very sure the problem is somewhere in rsync. Bernd -- Bernd Hohmann Organisationsprogrammierer Höhenstrasse 2 * 61130 Nidderau Telefon: 0

Re: -e escape rule

2016-10-20 Thread Kevin Korb
The \ escapes are for the shell. Rsync never sees them and therefore can't honor them. On 10/20/2016 05:24 AM, Samuel Williams wrote: > Hello, > > I'm using Ruby's Shellwords module, which generates a string from an > array, suitable for shell evaluation. > > Ruby's implementation prefers escap

Re: -e escape rule

2016-10-20 Thread Dave Howorth
On 2016-10-20 10:24, Samuel Williams wrote: Hello, I'm using Ruby's Shellwords module, which generates a string from an array, suitable for shell evaluation. Ruby's implementation prefers escaping whitespace with a backslash rather than quotes. However, this appears to cause some kind of issue

Re: -e escape rule

2016-10-20 Thread Samuel Williams
> There's no reason to escape an "=" sign in the above command. Okay, so at a certain level I agree with you and that's how I've fixed the issue. All the stuff about config files is not feasible for a variety of reasons - I'm aware of those options. I appreciate that you took the time to explain

Re: -e escape rule

2016-10-20 Thread Paul Slootman
On Thu 20 Oct 2016, Samuel Williams wrote: > > I'm using Ruby's Shellwords module, which generates a string from an > array, suitable for shell evaluation. > > Ruby's implementation prefers escaping whitespace with a backslash > rather than quotes. However, this appears to cause some kind of issu

-e escape rule

2016-10-20 Thread Samuel Williams
Hello, I'm using Ruby's Shellwords module, which generates a string from an array, suitable for shell evaluation. Ruby's implementation prefers escaping whitespace with a backslash rather than quotes. However, this appears to cause some kind of issue in Rsync when it computes argv from -e option.