SGID fails to set w permission for the group

eantoranz · 01-29-2008, 03:33 PM

I'm trying to set up a CVS repository.

I want newly created directories to be readable by the group that the repository belongs to. That's what the SGID bit is used for, right?

Well, look at this:

Code:

antoranz@somos-server:/var/cvs2$ ls -lad ./
drwxrws--- 3 root desarrollo2 4096 2008-01-29 16:51 ./
antoranz@somos-server:/var/cvs2$ ls -l
total 4
drwxrws--- 3 root desarrollo2 4096 2008-01-29 16:14 CVSROOT
antoranz@somos-server:/var/cvs2$ mkdir test
antoranz@somos-server:/var/cvs2$ ls -l
total 8
drwxrws--- 3 root     desarrollo2 4096 2008-01-29 16:14 CVSROOT
drwxr-sr-x 2 antoranz desarrollo2 4096 2008-01-29 16:56 test

See? I have set up the SUID for the repository, the group has all permissions on the repository, but when I create a new directory inside the repository, the group permission fails to set the w bit (though the group does appear to be the "sticky" one), so other people can't write on my directory. What am I doing wrong?

Thanks in advance.

PS Same thing for new files. They fail to have the w bit for the group.

unSpawn · 01-29-2008, 07:56 PM

Quote:

Originally Posted by eantoranz

I want newly created directories to be readable by the group that the repository belongs to. That's what the SGID bit is used for, right?

That's what umask is for.

eantoranz · 01-30-2008, 07:46 AM

So I have to change the UMASK?

I had thought about that already... setting the umask to 002 is advisable on a systemwide setting (like in /etc/profile)?

unSpawn · 02-01-2008, 06:15 AM

You can force a separate umask for specific users if you think 0002 is too wide open, but indeed, /etc/profile, or /etc/profile.d/* if their shell honours it.