| To: | Jakob Østergaard <joe@xxxxxxxxxxxx> |
|---|---|
| Subject: | Re: fchown permission check bug |
| From: | Steve Lord <lord@xxxxxxx> |
| Date: | Mon, 27 Mar 2006 10:13:35 -0600 |
| Cc: | linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <44280DA1.20506@xxxxxxxxxxxx> |
| References: | <4427BEFD.5060509@xxxxxxxxxxxx> <442809EF.2010009@xxxxxxx> <44280DA1.20506@xxxxxxxxxxxx> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
| User-agent: | Thunderbird 1.5 (X11/20051201) |
Jakob Østergaard wrote: Steve Lord wrote:Check the value of /proc/sys/fs/xfs/restrict_chown, this should be 1 to enablethis.# cat /proc/sys/fs/xfs/restrict_chown 1That's how it is, on the affected machine. Should it be 0? Is there any good reason why XFS by default behaves differently from ext3 on this? (As a naïve user I'd expect CAP_CHOWN to allow fchown ;)Thanks, Default should be the same as ext3 and CAP_CHOWN should be working. Steve |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | exclusion of trees with xfsdump, Rumi Szabolcs |
|---|---|
| Next by Date: | Re: fchown permission check bug, Steve Lord |
| Previous by Thread: | Re: fchown permission check bug, Jakob Østergaard |
| Next by Thread: | [no subject], Guk-Bong Kwon |
| Indexes: | [Date] [Thread] [Top] [All Lists] |