Bug 331891 - rsync hangs with verbosity higher then 2
Summary: rsync hangs with verbosity higher then 2
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: rsync
Version: 4.0
Hardware: i386
OS: Linux
low
low
Target Milestone: ---
: ---
Assignee: Jan Zeleny
QA Contact:
URL:
Whiteboard:
Depends On: 140462
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-10-15 07:44 UTC by Jose Plans
Modified: 2018-10-20 00:50 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-03-05 10:22:05 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
rsync-2.6.4-three-verbosity.patch (3.83 KB, patch)
2007-10-15 07:44 UTC, Jose Plans 		no flags Details | Diff
View All

Comment 1 Jose Plans 2007-10-15 07:44:54 UTC 
Created attachment 227361 [details]
rsync-2.6.4-three-verbosity.patch
Comment 4 RHEL Program Management 2008-02-01 19:01:21 UTC 
This request was evaluated by Red Hat Product Management for
inclusion, but this component is not scheduled to be updated in
the current Red Hat Enterprise Linux release. If you would like
this request to be reviewed for the next minor release, ask your
support representative to set the next rhel-x.y flag to "?".
Comment 6 RHEL Program Management 2008-03-19 05:47:44 UTC 
This request was evaluated by Red Hat Product Management for
inclusion, but this component is not scheduled to be updated in
the current Red Hat Enterprise Linux release. If you would like
this request to be reviewed for the next minor release, ask your
support representative to set the next rhel-x.y flag to "?".
Comment 9 Jan Zeleny 2010-03-05 10:22:05 UTC 
Since this issue seems to be rather small and there is only one more release for RHEL4 planned, I'm closing this bug as WONTFIX. If anyone encounters this problem, I recommend switching to RHEL5. According to upstream, this has been fixed in rsync-2.6.4 and there is 2.6.8 version present in RHEL5, so it should be ok there.
Note You need to log in before you can comment on or make changes to this bug.