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 jw schultz
On Tue, Mar 04, 2003 at 03:59:07PM +0100, Philipp W. wrote: > > 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,

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

Re: 6c6c

2003-03-04 Thread jw schultz
Sending direct to me what should be going to the list is a sure way to get a low priority in my queue. On Mon, Mar 03, 2003 at 03:02:47PM +0100, Philipp W. wrote: > > Very strange. My first thought was a bad terminal settting > > and oddly enough u8 (user string 8) could do that but i > > can't s

Re: 6c6c

2003-03-03 Thread jw schultz
On Mon, Mar 03, 2003 at 02:02:06PM +0100, Philipp W. wrote: > Has anyone an idea why i always get > > 6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c6c