At 07:44 18.01.2011 -0800, you wrote:
In 5.2.0.9.1.20110118091956.04afb940@localhost, on 01/18/11
at 09:32 AM, Fabian Cenedese cened...@indel.ch said:
Hi,
Is it possible that SSH -i key could also be scanned by rsync and
interpreted as --itemize?
That is what is happening. You have
-e
In 5.2.0.9.1.20110119091636.04a65ae0@localhost, on 01/19/11
at 09:17 AM, Fabian Cenedese cened...@indel.ch said:
Hi,
I use the same construct in other scripts without having this problem. So
I think the escaping is already correct. The main reason might be the
logfile command as Matt pointed
Hi
From reading the man pages I couldn't find such a hint, but is
there a way that --itemize is implicitely activated e.g. with using
another parameter?
Is it possible that SSH -i key could also be scanned by rsync
and interpreted as --itemize?
Can it be switched off again with --no-i? That
On Tue, 2011-01-18 at 09:32 +0100, Fabian Cenedese wrote:
From reading the man pages I couldn't find such a hint, but is
there a way that --itemize is implicitely activated e.g. with using
another parameter?
I used these params in a script with rsync 3.0.3pre1 on a NAS.
MYRSYNC_ARGS=-rptgo
