This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: rsh no longer works with rsync as of 1.5.9


On Mon, 29 Mar 2004, Bruce Dobrin wrote:

> On Fri, 26 Mar 2004, Igor Pechtchanski wrote:
>
> >Re: rsh no longer works with rsync as of 1.5.9
> >From: Igor Pechtchanski <pechtcha at cs dot nyu dot edu>
> >To: Bruce Dobrin <dobrin at imageworks dot com>
> >Cc: cygwin at cygwin dot com
> >Date: Fri, 26 Mar 2004 23:33:05 -0500 (EST)
> >Subject: Re: rsh no longer works with rsync as of 1.5.9
> >References: <00ec01c41387$02143d10$4d1f1cac@THEODOLITE>
> >Reply-to: cygwin at cygwin dot com
>
> >On Fri, 26 Mar 2004, Bruce Dobrin wrote:
>
> >> Hi,
> >>
> >> I have been using rsync via rsh (-e "rsh")   for our general distributions
> >> for a for all of our windows and Linux machines ( 2000 of them) .   on
> >> Upgrading from cygwin1.5.5 to 1.5.9,  Rsync could no longer use rsh to
> >> rsync.
> >>
> >> I get : "rsh : unknown option -- server"
> >> I down graded the rsync2.6.0 from the cyg1.5.9 install to the 2.5.6 version
> >> from the cyg1.5.5 version and got the same problem.  I restored the rsync to
> >> 2.6.0 and copied the rsh.exe from the inetutils-1.3.2-25 from the cyg1.5.5
> >> install and rsync started working again.
> >>
> >> Is there a known bug or known workaround for using the most recent version
> >> of rsh ( from 1.3.2-26)?
> >> thanks.
> >> Bruce Dobrin
> >>
> >> example: rsync -rluzv -e "rsh" --timeout=100 --size-only matilda:/c/dist_and_install_files/dist/sysadm_general/ /c/
> >>
> >> rsh : unknown option -- server
> ?>
> >WAG: check text/binary settings on the connection (e.g., does $CYGWIN
> >contain "nobinmode"?).  Also check with ssh.
> >Igor
>
> Igor,
> Thank you for answering.
> Using ssh works fine ( well, it works as well as rsync has ever worked
> anyway ;-)  ). My $CYGWIN is a fairly standard : binmode tty ntsec
>
> ssh is not really an option for us though;our facility is locked down hard
> so internally we don't use ssh at all but depend on rsh..  I'd like to keep
> our rsh current though,  but to keep it working I have had to replace the
> newer rsh with the older one...  eventually I'm afraid this will bite me in
> the butt.   should I talk to the rsync people?  it looks like rsync is
> passing a switch "--server" that is being picked up incorrectly by the newer
> rsh and not the older one...   ( if I type:  BASH > rsh --server
> I get the same response:  "rsh: unknown option -- server" ),
>
> Thanks for your continuing help
> Bruce---

Oh.  This may have something to do with the argument permutation in the
"getopt" call, which was introduced at some point.  Try (a) setting the
POSIXLY_CORRECT environment variable before calling rsync, or (b) giving
the '-e "rsh --"' option instead of '-e "rsh"' (don't know if rsync will
allow this, though).
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha@cs.nyu.edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor@watson.ibm.com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski, Ph.D.
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster."  -- Patrick Naughton

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]