Re: Always exitcode 256 under Cygwin with rsync 2.6.4

2005-04-04 Thread Benjamin Watkins
Joost van den Broek wrote: I can confirm too that this has solved the problem for me. It's time for a new cwRsync release :) - Joost If Tev is going to release a new cwRsync, I might ask that he adds the patch Wayne made for the problem I experienced with multiplexing errors. This appears

Re: Always exitcode 256 under Cygwin with rsync 2.6.4

2005-04-04 Thread Joost van den Broek
On Monday 4 April 2005 16:39, Paul Haas wrote: > > If I understand the problem, it looks like it is fixed in Cygwin 1.5.14-1, > which was released sometime on Saturday. > > http://cygwin.com/ml/cygwin/2005-04/msg00073.html > > The Cygwin 1.5.14-1 announcement includes this change: > > - cgf: Righ

Re: Always exitcode 256 under Cygwin with rsync 2.6.4

2005-04-04 Thread Benjamin Watkins
Paul Haas wrote: On Sun, 3 Apr 2005, Wayne Davison wrote: On Mon, Apr 04, 2005 at 07:28:02AM +0200, Joost van den Broek wrote: When you just give an empty rsync command, it should also exit with an exit code (1). But the errorlevel gets set to no. 256 instead. As mentioned in the other message tha

Re: Always exitcode 256 under Cygwin with rsync 2.6.4

2005-04-04 Thread Paul Haas
On Sun, 3 Apr 2005, Wayne Davison wrote: On Mon, Apr 04, 2005 at 07:28:02AM +0200, Joost van den Broek wrote: When you just give an empty rsync command, it should also exit with an exit code (1). But the errorlevel gets set to no. 256 instead. As mentioned in the other message that brought this up,

Re: Always exitcode 256 under Cygwin with rsync 2.6.4

2005-04-04 Thread Shachar Shemesh
Wayne Davison wrote: On Mon, Apr 04, 2005 at 07:28:02AM +0200, Joost van den Broek wrote: When you just give an empty rsync command, it should also exit with an exit code (1). But the errorlevel gets set to no. 256 instead. As mentioned in the other message that brought this up, I assume th

Re: Always exitcode 256 under Cygwin with rsync 2.6.4

2005-04-03 Thread Wayne Davison
On Mon, Apr 04, 2005 at 07:28:02AM +0200, Joost van den Broek wrote: > When you just give an empty rsync command, it should also exit with an > exit code (1). But the errorlevel gets set to no. 256 instead. As mentioned in the other message that brought this up, I assume that this is something wro

Always exitcode 256 under Cygwin with rsync 2.6.4

2005-04-03 Thread Joost van den Broek
I've upgraded all my Windows servers with the new released cwRsync version, so they're all running the latest rsync now. But this version seems to ignore exitcodes, since my batchscript does not restart the job when a timeout occurs. Before, rsync did set the errorlevel on exit, so my script kne