STDERR vs STDOUT?

[Dave Dykstra]

On Fri, Feb 15, 2002 at 11:44:32AM -0500, Mack, Daemian wrote:
> Hi all.  I'm writing an installation script that uses Cygwin's bash.exe to
> launch an rsync.exe process, which is passed arguments.  This performs an
> rsync over the Internet.
> 
> I'd like to capture stdout to one file, and stderr to another, so that I can
> have a clean log of any errors.  However, rsync.exe's use of file
> descriptors isn't jiving with my understanding of them.
> 
> If I tell rsync to sync with a module that I know is not there in order to
> generate an error, error.log is empty, and success.log contains @ERROR:
> Unknown module 'whatever.'  Here's the command I'm using:
> 
> 
> ./rsync.exe -a -c -v -t username at 10.10.10.1::whatever /cygdrive/c/stuff >
> success.log 2>error.log
> 
> 
> I can't claim mastery over file descriptors, but is this expected behavior?
> At the moment, I'm at a loss as to how to capture errors to their own file.


That's the way it is, but I think it's a bug.  I went ahead and checked in
a fix to the rsync CVS:
    http://cvs.samba.org/cgi-bin/cvsweb/rsync/clientserver.c.diff?r1=1.84&r2=1.85

- Dave Dykstra