Bug 2722 - chown/chgrp different behavior on bad symlinks
chown/chgrp different behavior on bad symlinks
Status: CLOSED CURRENTRELEASE
Product: Red Hat Linux
Classification: Retired
Component: fileutils (Show other bugs)
6.0
All Linux
medium Severity medium
: ---
: ---
Assigned To: Cristian Gafton
:
: 2374 (view as bug list)
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 1999-05-10 17:03 EDT by Cristian Gafton
Modified: 2008-05-01 11:37 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 1999-10-04 12:37:10 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 Cristian Gafton 1999-05-10 17:03:09 EDT
chown -f exits with a 0 on a bad symlink
chgrp -f does not
Comment 1 Jeff Johnson 1999-05-11 10:51:59 EDT
*** Bug 2374 has been marked as a duplicate of this bug. ***

the fixperms macro bombs out if chown or chgrp fails.  This
isn't the behaviour that RPM 2.5 had.  While it is only a
configuration issue, it seems to make sense to me that the
default behaviour is to be backwards compatible with 2.5.
Comment 2 Cristian Gafton 2001-02-07 19:35:04 EST
Seems to work since at least 6.2...

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