Paul Eggert wrote:
> Karl Berry wrote:
> > I was on centos7.
> >
> > (I don't observe your problem on my Fedora 31 box, for example).
> >
> > Maybe there is hope for a future centos, then.
Just another few data points...
I was able to recreate this issue on a CentOS 7 system running in a
On 9/1/20 3:30 PM, Karl Berry wrote:
I was on centos7.
(I don't observe your problem on my Fedora 31 box, for example).
Maybe there is hope for a future centos, then.
Maybe. Or it could be a filesystem or mounting issue. My filesystem was ext4
mounted rw,relatime,seclabel, for what
So partly this is a platform issue
I was on centos7.
(I don't observe your problem on my Fedora 31 box, for example).
Maybe there is hope for a future centos, then.
adding a run-time option to the chown and chgrp commands. Not sure
it's worth it.
Agreed about not being worth
On 9/1/20 2:25 PM, Karl Berry wrote:
Is it necessary for chgrp to clear setgid on directories even when the
group is not actually changed? In my life at least, it is rather
annoying.
The chgrp command isn't doing that directly; it's merely invoking the fchownat
syscall, and the syscall is
Is it necessary for chgrp to clear setgid on directories even when the
group is not actually changed? In my life at least, it is rather
annoying. --thanks, karl.
$ mkdir foo
$ chmod g+s foo
$ ls -ld foo
drwxrwsr-x 2 karl root 6 Sep 1 10:36 foo/
$ chgrp root foo
$ ls -ld foo
drwxrwxr-x 2 karl
