On Sat, Nov 17, 2012 at 11:20:21AM -0500, Ryan Stone wrote: > Wow. So apparently things are even more broken than I though. Let's play, > "What group am I in?" > > root_at_group-testing:/usr/home/rstone # cd /tmp > root_at_group-testing:/tmp # pw groupadd testing > root_at_group-testing:/tmp # mkdir testdir > root_at_group-testing:/tmp # chown root:testing testdir/ > root_at_group-testing:/tmp # chmod g+rwx testdir/ > root_at_group-testing:/tmp # pw usermod > root_at_group-testing:/tmp # pw groupmod testing -m rstone > root_at_group-testing:/tmp # id rstone > uid=1001(rstone) gid=1001(rstone) groups=1001(rstone),0(wheel),1002(testing) > root_at_group-testing:/tmp # exit > $ id > uid=1001(rstone) gid=1001 groups=1001,0 > $ id rstone > uid=1001(rstone) gid=1001 groups=1001 > $ touch /tmp/testdir/testfile > touch: /tmp/testdir/testfile: Permission denied > $ ls -ld /tmp/testdir/ > drwxrwxr-x 2 root 1002 512 Nov 17 11:07 /tmp/testdir/ > This is not a bug and I think it always was this way. The process you used to su/sudo/whatever to root was not in testing group and didn't magically enter it after you added rstone user to that group. You have to log in again or do stuff like exec su - rstone. -- Mateusz Guzik <mjguzik gmail.com>Received on Sat Nov 17 2012 - 16:28:19 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:32 UTC