Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 87860 - rcp isn't large file enabled
rcp isn't large file enabled
Status: CLOSED DUPLICATE of bug 67362
Product: Red Hat Linux
Classification: Retired
Component: rsh (Show other bugs)
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Phil Knirsch
Ben Levenson
Depends On:
  Show dependency treegraph
Reported: 2003-04-03 04:38 EST by steigerwald
Modified: 2015-03-04 20:12 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-21 13:52:27 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description steigerwald 2003-04-03 04:38:08 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.0.1) Gecko/20020920

Description of problem:
It ist not possible to 'rcp' files larger then 2GB.
You will get an error message like:
rcp: test2.3G: File too large 

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

How reproducible:

Steps to Reproduce:
1.create an file with a size larger then 2 GB
2.rcp <file> ws1:/tmp
3.=> error messages 

Actual Results:  rcp: test2.3G: File too large 

Expected Results:  it is necessary to recompile the rsh-0.17-10 rpm package
using using the "Large-File enabled Option"

Additional info:
Comment 1 steigerwald 2003-04-03 07:26:02 EST
- There will be the same problem with the rdist- command.
- It's also no possible to get files larger then 2GB
(This could be the same problem within the rsh-server-0.17-10 package )
Comment 2 Phil Knirsch 2003-06-25 11:04:32 EDT

*** This bug has been marked as a duplicate of 67362 ***
Comment 3 Red Hat Bugzilla 2006-02-21 13:52:27 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

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