Marco Weber wrote:
yes you need umask as well... so the complete example would be: mkdir /home/agroup chgrp agroup /home/agroup chmod -R 6774 /home/agroup cd /home/agroup umask 002 marco weber
Thanks,Maybe I am not understanding something here. If I do that or what the other person posted I don't get the results I am after with only 1 directory. It just sets it for everything regaurdless. An example of it not working is like so;
(project dir is a symlink) # pwd /home/user # touch test # ls -l -rw-r--r-- 1 user user 0 Jul 21 00:42 test (right) # cd project # touch test # ls -l -rw-r--r-- 1 user group 0 Jul 21 00:42 test (wrong) # umask 002 /home/user/project # cd .. # touch test2 # ls -l -rw-r--r-- 1 user user 0 Jul 21 00:42 test (right) -rw-rw-r-- 1 user user 0 Jul 21 00:42 test2 (wrong) # pwd /home/user # cd project # touch test2 # ls -l -rw-r--r-- 1 user group 0 Jul 21 00:42 test (wrong) -rw-rw-r-- 1 user group 0 Jul 21 00:42 test (right)i need to umask 002 for the project dir and a umask of 022 for everything else. I only want it to set files in 'project' to be read/write from the group, everything else should be read/write from the user and read from the group like normal.
Thanks Mike