In <5.2.0.9.1.20110118091956.04afb940 at localhost>, on 01/18/11 at 09:32 AM, Fabian Cenedese <Cenedese at 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 "$SSH" and your shell is interpreting this as multiple arguments after expansion. Depending on your shell, changing this to -e \""$SSH"\" might be sufficient to avoid the issue. Steven -- ---------------------------------------------------------------------- "Steven Levine" <steve53 at earthlink.net> eCS/Warp/DIY etc. www.scoug.com www.ecomstation.com ----------------------------------------------------------------------
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 --stats --modify-window=1 --timeout=1800 --log-file=/tmp/rsbackup.log --rsync-path="/path/to/rsync" --timeout=3600" > SSH="ssh -l user -ax -i /path/to/key -o ClearAllForwardings=yes -o StrictHostKeyChecking=no" > > rsync $MYRSYNC_ARGS -l --delete -e "$SSH" --no-i $SOURCE/mod $DEST:$SOURCE/mod & > > And that still results in: > 2011/01/17 20:00:08 [3918] .d..t...... server/Directory/ > 2011/01/17 20:00:13 [3918] <f..t...... server/Directory/File > etc
At 07:44 18.01.2011 -0800, you wrote:>In <5.2.0.9.1.20110118091956.04afb940 at localhost>, on 01/18/11 > at 09:32 AM, Fabian Cenedese <Cenedese at 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 "$SSH" > >and your shell is interpreting this as multiple arguments after expansion. >Depending on your shell, changing this to > > -e \""$SSH"\" > >might be sufficient to avoid the issue.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 out. I will try and see. Thanks bye Fabi