On 12/31/2012 07:27 PM, Rob Townley wrote:
On Fri, Dec 28, 2012 at 9:10 AM, Craig Whitecraig.white@ttiltd.com wrote:
I guess I'm not sure what the point is by having files owned by 'nobody' and then adding nobody 'user' to the 'users' group - that seems to be some rather twisted logic that has security implications far beyond the simple samba share configuration but hey… it's your box.
chirp users /data/public -R chmod g+s /data/public -R
will ensure that all files/folders in /data/public are owned by the group 'users' and any new files/folders created within (whether by samba or not) belong to that group.
if you add 'inherit permissions = yes' to the 'share' definition in smb.conf, that also will impact. Yes, you could also add: force security mode = 770 #or 775 force directory security mode = 770 #or 775 within the share definition too.
What is the chirp command and where is it found? "yum search all chirp" yielded nothing.
I believe you will find that chirp was a fat finger for chgrp.