Did you try setting the g+ws bit on the directory and set umask to 002? Here's an example:
# cd / # mkdir samba # chmod g+ws samba # chgrp users samba # vi /etc/profile ... // set umask to 002 # grep umask /etc/profile # The global umask value is stored in /etc/login.defs and # will be set by pam_umask.so (see "man pam_umask"). umask 002 # su mikemac mikemac:> cd /samba mikemac:> touch foo mikemac:> mkdir bar mikemac:> ls -l total 4 drwxrwsr-x 2 mikemac users 4096 2011-05-04 10:12 bar -rw-rw-r-- 1 mikemac users 0 2011-05-04 10:11 foo mikemac:> cd bar mikemac> touch foo gpok191:/samba/bar # ls -l foo ls -l foo -rw-rw-r-- 1 mikemac users 0 2011-05-04 10:13 foo This "pushes down" R/W authority below /samba for the group named users. It's outside the scope of Samba, but may work fine, and then you wouldn't have to worry so much about the smb.conf settings. "Mike MacIsaac" <mike...@us.ibm.com> (845) 433-7061 ... > > We have tried several of the recommendations but still the files are created > as <userid> group users and only the owner has read/write on the files. Is > there anything else we can do?... ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
