[NTLUG:Discuss] force group ownership

[Paul Ingendorf]

I would check the permissions of the actual directories.  Based off your setup here they should not be able to create or modify any kind of files.  Of course now that I think about it could be caused by the whole public = yes flag but I'm not for sure right now.  I would first check the permissions of the directory itself and make sure it is not 777 I would also remove the whole public = yes flag and see how that works.  I think I just took that from a config you posted for that share but I don't think it would be required for what your doing esp given that your forcing the group here.

-----Original Message-----
From: discuss-admin at ntlug.org [mailto:discuss-admin at ntlug.org]On Behalf
Of Bobby Wrenn
Sent: Thursday, February 07, 2002 4:51 PM
To: discuss at ntlug.org
Subject: Re: [NTLUG:Discuss] force group ownership


Just one more thing. Valis users can now write to the samba share.
Invalid users now get mapped to nobody and cannot alter files in the
directory. However, invalid users can create 0byte files in the
directory.

Can I stop that?
Here is the current configuration of the share:

[public]
   volume = Planning
   browseable = yes
   comment = Product Data
   path = /home/planning
   public = yes
   guest ok = yes
   writable = no
   write list = @planning
   read list = nobody guest
   force group = planning
   create mask = 0664
   directory mask = 0775
   security mask = 0775

_______________________________________________
http://www.ntlug.org/mailman/listinfo/discuss