rsync error: unexplained error

[drstaples at beckman.com]

JW,

Sorry for p*ssing you off, that was not my intention.

I looked at the archives and saw no resolution to this specific problem in
any of the rsync-2.5.3-NEWS, rsync-2.5.4-NEWS or rsync-2.5.5-NEWS files.

I am somewhat new to the *NIX environment and don't yet understand all
the tools or protocols (CVS, diff(1), patch(1)) or how they work.

However, I did just download from ftp.samba.org/ftp/rsync the 2.5.5 source
(not sure this is where I should be getting it from or not).  In any event, the
source that exist there (with regard to handling terminating children) is no
different from the 2.5.2 version.

I will look into how to properly format the changes for diff(1) and/or patch(1).
I would appreciate it if someone would let me know how and to where I should
submit the changes for incorporation into the product.

Dave



                                                                                                                                 
                    "jw schultz"                                                                                                 
                    <jw at pegasys.ws       To:     "David R. Staples" <drstapl at empirenet.com>                                      
                    >                    cc:     rsync at samba.org, drstaples at beckman.com                                          
                                         Subject:     Re: rsync error: unexplained error                                         
                    09/01/02 05:34                                                                                               
                    PM                                                                                                           
                                                                                                                                 
                                                                                                                                 




To start with, use the carrage return and don't send html.

This sounds like a problem that was fixed a few months ago.
You might try searching archives.  Upgrade to current
(2.5.5) or the CVS tree.

And please send any changes as diff -u against up-to-date
CVS (see diff(1) and patch(1)) encoded as text/plain or flat
ascii.  With what you sent it is unclear what you changed
and requires much work to apply changes.