samba - Dec 2012 - Permissions problem

Hi,

	I've got a strange behaviour on a share when I copy files with files 
explorers (like Thunar, Nautilus, ...).

	This is the share configuration :
	[share1]
		comment = Share 01
		path = /home/shares/share1
		valid users = +share1
		force group = share1
		read only = No
		create mask = 0660
		force create mode = 0660
		directory mask = 1770
		force directory mode = 1770
		browseable = No
		strict locking = Yes

	When I copy/paste a file from my computer (which has 444 mode) to the 
share the resultant file has 444 mode (instead of the 660 expected).

	I think the mode was changed by the file explorer 'cause when the file 
was created on the share (and during the copy process) the mode is 660 
(like expected) it's just at the end of the copy that the mode was 
change to reflect mode of the source file.

	If I copy this file in command line the mode is 660 as expected, If I 
want to simulate the file explorer behaviour I must do a 'cp 
--preserve=mode' copy.

	Is there a way to forbid this behaviour ? Or is there something wrong 
in my configuration ?

	Thanx by advance,
	Regards
	Bruno


-- 

Bruno MACADRE
-------------------------------------------------------------------
  Ing?nieur Syst?mes et R?seau     | Systems and Network Engineer
  D?partement Informatique         | Department of computer science
  Responsable R?seau et T?l?phonie | Telecom and Network Manager
  Universit? de Rouen              | University of Rouen
-------------------------------------------------------------------
Coordonn?es / Contact :
	Universit? de Rouen
	Facult? des Sciences et Techniques - Madrillet
	Avenue de l'Universit? - BP12
	76801 St Etienne du Rouvray CEDEX
	FRANCE

	T?l : +33 (0)2-32-95-51-86
	Fax : +33 (0)2-32-95-51-87
-------------------------------------------------------------------

On 12/20/2012 10:05 AM, Bruno MACADRE wrote:
> If I copy this file in command line the mode is 660 as expected, If I
> want to simulate the file explorer behaviour I must do a 'cp
> --preserve=mode' copy.
> 
>     Is there a way to forbid this behaviour ? Or is there something
> wrong in my configuration ?
The only way that I could think of would be to write a Samba VFS module
that prevented invocation of the chown(2) and chmod(2) system calls (and
friends).  Such a VFS module would need to return a suitable error code,
which would more than likely then be passed back to the client.

Or you could simply "stub" the chown/chmod (and friends!) system calls
such that they return success but are effectively no-ops.

Someone else with more intimate experience with Samba's code may have a
better option, but that's the only one I can think of at the moment.

	HTH,
	Mike