On Tue, Apr 17, 2012 at 12:56:58AM -0300, rhatto wrote: > Em Sun, Apr 15, 2012 at 04:26:27PM +0200, Paul van Tilburg escreveu: > > I meant this differently. It just seems that if you make an error, e.g. > > you set: > > > > rsync_options = --non-existing-bla --syntax-error-coming up > > > > and rsync bails out, or maybe segvs or whatever, backupninja happily > > reports via email: SUCCES. > > Yes, that's another issue: https://labs.riseup.net/code/issues/3892
Ok. I know that the "moreutils" package in Debian has the mispipe tool[1] to return the exit code of the first program rather than the latter. Maybe this tool or its source code is useful. 1: http://packages.debian.org/source/unstable/moreutils > > I am reluctant to apply this... why also first $created but \$created in > > the second hunk? > > The second hunk refers to code to be executed in the remote side, so it has > to be escaped to not evaluate at the local side. > > Maybe would be better to wait me to sort out the most important rsync handler > issues and then give you a single patch to try so I don't bother you too much > with my development as I already did. :/ Ok, it's no problem. I was just indicating this to mention that my results may become unreliable at some point due to this. But I keep a "rsync.orig" file to compare, and sometimes I patch by commenting out the old code. I think it's still good. :) Paul -- Using the Power of Debian GNU/Linux | E-mail: pau...@debian.org Jabber/GTalk: p...@luon.net | GnuPG key ID: 0x50064181
signature.asc
Description: Digital signature
