search for: 2a384495

Displaying 1 result from an estimated 1 matches for "2a384495".

Did you mean: 2.84495
2014 Aug 30
1
Cleanest way to find out if it was a --dry-run
Hi, As far as I can see, the only way you can tell it's been a dry-run at the receiver-side, is to parse RSYNC_ARGs in the pre-xfer script. I think the only way is to crawl through the RSYNC_ARGs to find a value which: - starts with a single dash, and; - contains 'n', and; - comes prior to the "." value, signifying the start of the 'path args' (which seem inherently