Bug 113397
Summary: | sgid directory changes permission when files are copied, created but not moved | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 3 | Reporter: | Xander D Harkness <harkness> |
Component: | kernel | Assignee: | Stephen Tweedie <sct> |
Status: | CLOSED NOTABUG | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.0 | CC: | nobody |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-01-15 11:31:07 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Xander D Harkness
2004-01-13 15:40:51 UTC
Nothing to do with the 'mv' command, but the 'rename' syscall. "mv" simply renames a file. It doesn't change the file at all. This is correct behaviour. The sgid bit on a directory only affects the gid assigned to *new* files created inside that directory. That's why copy and create both set the gid. Moving an existing file is not expected to change the gid. |