Re: 6c6c

2003-03-04 Thread Philipp W.
>> 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 syntax for your shell (it is for bash) > then it isn't comi

Re: 6c6c

2003-03-04 Thread Philipp W.
>> 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 syntax for your shell (it is for bash) > then it isn't comi

Re: 6c6c

2003-03-04 Thread Philipp W.
> However RH7.3 would i think have 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. it was 2.5.4, now i compiled 2.5.6 with the same issues... > You didn't say if this

6c6c

2003-03-03 Thread Philipp W.
Has anyone an idea why i always get 6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c

Human Readable

2002-10-24 Thread Philipp W.
Hi! I'mn quiet new to rsync... i'm usig it for making bakups over internet. What i'd like is to add som other output-possibilities... What's in my interest is, how many bytes are transferred and how long it needed. So i've written myself the -Hr option to get --stats output formated in a bette