>> i think stdout as
>> rsync -avvP MCI/ MCI2 --stats --delete 1>1.txt
>> doesn't give me the 6c6c on the command line nor in the 1.txt
>>
>> rsync -avvP MCI/ MCI2 --stats --delete 2>1.txt
>> leaves an empty 1.txt.
>
> If that is the right s
>> i think stdout as
>> rsync -avvP MCI/ MCI2 --stats --delete 1>1.txt
>> doesn't give me the 6c6c on the command line nor in the 1.txt
>>
>> rsync -avvP MCI/ MCI2 --stats --delete 2>1.txt
>> leaves an empty 1.txt.
>
> If that is the right s
lready be fixed.
>
> it was 2.5.4, now i compiled 2.5.6
> with the same issues...
>
> > You didn't say if this was on stdout or stderr.
>
> i think stdout as
> rsync -avvP MCI/ MCI2 --stats --delete 1>1.txt
> doesn't give me the 6c6c on the command line
t; You didn't say if this was on stdout or stderr.
i think stdout as
rsync -avvP MCI/ MCI2 --stats --delete 1>1.txt
doesn't give me the 6c6c on the command line nor in the 1.txt
rsync -avvP MCI/ MCI2 --stats --delete 2>1.txt
leaves an empty 1.txt.
>> i changed the dirs a
a very old version of
rsync. I'd start by upgrading. Certainly there isn't much
value of anyone spelunking the current code to fix a problem
that might already be fixed.
> i did some tests
You didn't say if this was on stdout or stderr.
> i changed the dirs ano got the same err
On Mon, Mar 03, 2003 at 02:02:06PM +0100, Philipp W. wrote:
> Has anyone an idea why i always get
>
> 6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c
Has anyone an idea why i always get
6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c
