Bug 16336 - cp -f does not force
cp -f does not force
Status: CLOSED NOTABUG
Product: Red Hat Linux
Classification: Retired
Component: fileutils (Show other bugs)
7.0
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Bernhard Rosenkraenzer
:
: 16337 (view as bug list)
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2000-08-16 09:30 EDT by Marius Bezuidenhout
Modified: 2008-05-01 11:37 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2000-10-03 10:31:20 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Marius Bezuidenhout 2000-08-16 09:30:19 EDT
Doing a copy with the force flag '-f' does nothing.
Comment 1 Marius Bezuidenhout 2000-08-16 09:36:41 EDT
*** Bug 16337 has been marked as a duplicate of this bug. ***
Comment 2 Tim Waugh 2000-08-16 11:04:14 EDT
As root, cp is aliased to 'cp -i', so when you type 'cp -f ...' it's actually
doing a 'cp -i -f ...'.
Comment 3 Marius Bezuidenhout 2000-08-17 02:44:24 EDT
But it worked in RedHat 6.2.
Should the force not take priority?
Other users should also have "alias cp='cp -i'"
Comment 4 Alan Cox 2000-08-18 12:49:22 EDT
The new behaviour is valid. Its certainly not desirable however
Comment 5 Marius Bezuidenhout 2000-08-21 03:28:51 EDT
Doing a `rm -i -f` does force.
Thus it is expected from `cp -i -f` as well.
Comment 6 Tim Waugh 2000-10-03 10:31:17 EDT
The cp from fileutils-4.0z has this:

-f, --force   if a preexisting destination file cannot be opened, then unlink it
and try again
...
--remove-destination  unlink each preexisting destination file before attempting
to open it (contrast with --force)
Comment 7 Bernhard Rosenkraenzer 2000-10-09 06:00:47 EDT
Check the fileutils changelog - it is intended behavior because of POSIX
compliance.

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