>
> So this disable a lot of interest in Rsync :-( Isn't there a way to
> disable
> "--whole-file"?
>
"--no-whole-file" should do it though for local copies, forcing delta
transfer is not going to speed up anything in most cases.
Selva
--
Please use reply-all for most replies to avoid omitting
On Sun, Jan 24, 2016 at 4:48 PM, <
dbonde+forum+rsync.lists.samba@gmail.com> wrote:
> That doesn't make sense. Both the source and destination path contains
> simple alphanumeric characters, no more no less. Why would it matter
> whether the path is /abc/ or /def/ or even /123/?
Hmm.. I thou
On Sun, Jan 24, 2016 at 12:29 PM, <
dbonde+forum+rsync.lists.samba@gmail.com> wrote:
> On 2016-01-24 03:51, Kevin Korb wrote:
>
>> Are you rsyncing from one to the other? Both of them to somewhere
>> else? One at a time to somewhere else? Why won't you just show your
>> actual command line
;Can anyone tell me how to do so??
>
I am afraid this is the wrong list. A post to the cwRsync user forum may
elicit some response..
Selva
>
> Thanks
>
>
>
> Richard
>
> On 10/13/2015 05:42 PM, Selva Nair wrote:
>
>> 2015-10-13 17:14 GMT-04:00 Richard Coutu
On Tue, Oct 13, 2015 at 5:03 PM, Xen wrote:
>
> As I said before, just rsyncing the lower layer (encrypted) of an eCryptfs
>> volume may work well -- no multiple decryption-encryption cycles and what
>> not.. Say you have an eCryptfs folder named ~/Private, then just keep your
>> images in ~/Priv
On Tue, Oct 13, 2015 at 12:54 PM, Xen wrote:
> Hi Folks,
>
> I was wondering if I could ask this question here.
>
> Initially when I was thinking up how to do this I was expecting block
> encryption to stay consistent from one 'encryption run' to the next, but I
> found out later that most scheme
On Sun, Jul 12, 2015 at 1:44 PM, Wayne Davison wrote:
> On Sat, Jul 11, 2015 at 1:16 PM Selva Nair wrote:
>
>> I had named a module as "global" and it appears not to be recognized.
>> [...] Any pointers as to what names are allowed for modules will be
>> ap
On Mon, Jul 13, 2015 at 5:19 PM, Simon Hobson
wrote:
> > What's needed is a file system that can do what hard links do, but at the
> > file page level. I imagine that this would work using the same Copy On
> > Write logic used in managing memory pages after a fork().
>
> Well some (all ?) enterp
Hi,
I had named a module as "global" and it appears not to be recognized. It
appears a section
[global]
path=xxx
etc.
is interpreted as global parameters and not as a module named global. Is
that the expected behaviour? Any pointers as to what names are allowed for
modules will be appreciated.
