Bug 62489 - warning *and* error if --rsh=prog is specified for rsync:// transfer
Summary: warning *and* error if --rsh=prog is specified for rsync:// transfer
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Public Beta
Classification: Retired
Component: rsync
Version: skipjack-beta1
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact: Aaron Brown
URL:
Whiteboard:
Depends On:
Blocks: 61901
TreeView+ depends on / blocked
 
Reported: 2002-04-01 18:28 UTC by Alexandre Oliva
Modified: 2014-03-17 02:26 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2002-04-01 21:22:38 UTC
Embargoed:


Attachments (Terms of Use)

Description Alexandre Oliva 2002-04-01 18:28:51 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020314

Description of problem:
Transfers using the rsync:// protocol disregard the --rsh=prog option, and they
warn so.  However, this option also causes a hard error at the end of the transfer.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1./usr/bin/rsync -r rsync://distro.ibiblio.org/redhat/rawhide/RedHat/ RedHat/  #
will transfer only an empty directory, no worries
2./usr/bin/rsync -e ssh -r rsync://distro.ibiblio.org/redhat/rawhide/RedHat/
RedHat/ # error
3./usr/bin/rsync --rsh ssh -r rsync://distro.ibiblio.org/redhat/rawhide/RedHat/
RedHat/ # error

Actual Results:  1.Successful transfer of an empty RPMS directory.  Exit status
is 0.
2 and 3:
WARNING: --rsh or -e option ignored when connecting to rsync daemon
[...]
rsync error: partial transfer (code 23) at main.c(893)

Exit status is non-zero.  Oops.

Expected Results:  The warning is appropriate, indeed, but the hard error is not.

Additional info:

Comment 1 Bill Nottingham 2002-04-11 03:52:23 UTC
Fixed in 2.5.4-2 - thanks!

Comment 2 Martin Pool 2002-04-15 07:51:33 UTC
Bill, I have your patch, it will be merged in upstream 2.5.6.


Note You need to log in before you can comment on or make changes to this bug.