The first thing that comes to mind is that the directory mask setting should 
not be 776 but 775 and the file create mask should be 664, not 776. 

Here is what the lengthy documentation of "man smb.conf" states: the "force 
create mask" should solve your problem. Also note at the end of the "create 
mask" documentation that Windows mode also enter in account. I would bet that 
in this case, the software is the one choosing the file permissions.

create mask (S)
              A synonym for this parameter is create mode .

              When a file is created, the  necessary  permissions
              are  calculated  according  to the mapping from DOS
              modes to UNIX permissions, and the  resulting  UNIX
              mode  is then bit-wise 'AND'ed with this parameter.
              This parameter may be thought of as a bit-wise MASK
              for  the UNIX modes of a file. Any bit not set here
              will be removed from the modes set on a  file  when
              it is created.

              The  default  value  of  this parameter removes the
              'group' and 'other' write and execute bits from the
              UNIX modes.

              Following  this  Samba  will bit-wise 'OR' the UNIX
              mode created from this parameter with the value  of
              the force create mode parameter which is set to 000
              by default.

              This parameter does not affect directory modes. See
              the parameter directory mode for details.

              See  also the force create mode parameter for forc�
              ing particular mode  bits  to  be  set  on  created
              files.  See  also the  directory mode parameter for
              masking mode bits on created directories. See  also
              the  inherit permissions parameter.

              Note  that this parameter does not apply to permis�
              sions set by Windows NT/2000 ACL  editors.  If  the
              administrator  wishes  to  enforce a mask on access
              control lists also, they need to set  the  security
              mask.

              Default: create mask = 0744

              Example: create mask = 0775

force create mode (S)
              This parameter specifies a set  of  UNIX  mode  bit
              permissions  that will always be set on a file cre�
              ated by Samba. This  is  done  by  bitwise  'OR'ing
              these  bits  onto  the  mode bits of a file that is
              being created or having  its  permissions  changed.
              The  default  for this parameter is (in octal) 000.
              The modes in this parameter are bitwise 'OR'ed onto
              the file mode after the mask set in the create mask
              parameter is applied.

              Note that by default this parameter does not  apply
              to  permissions set by Windows NT/2000 ACL editors.
              If the administrator wishes to enforce this mask on
              access  control  lists  also,  they need to set the
              restrict acl with mask to true.

              See also the parameter create mask for  details  on
              masking mode bits on files.

              See also the inherit permissions parameter.

              Default: force create mode = 000

              Example: force create mode = 0755

              would force all created files to have read and exe�
              cute permissions set for  'group'  and  'other'  as
              well  as  the  read/write/execute  bits set for the
              'user'.

       force directory mode (S)

Let me know if this helped.

Thanks.

G�rard Perreault
[EMAIL PROTECTED]

On Tuesday 26 February 2002 12:28, Wayne Stout wrote:
> Greetings, everyone.
> 
> I've got a strange little problem happening with file creation on one of my 
> Samba servers here. It's 100% repeatable, but makes absolutely no sense to 
> me. I've asked this on the RedHat list, but got no response, so I thought 
> I'd ask the good people of this list. Here's the situation.
> 
> My Marketing department has a scanner attatched to a WinNT4 box that they 
> do all of their image scanning through. They scan the image and save the 
> file locally on the scanner machine. They then open the file on their own 
> machines from the scanner box, make changes in Photoshop, and save the 
> file. Here's the weird part. If they save the file directly to the Samba 
> share, permissions are set to 006. However, if they save the file to their 
> desktops first, *then* copy it to the Samba share, perms are set to 766, as 
> shown below.
> 
> -rwxrw-rw- 1 tracy Market 454264 Feb 18 15:44 svp5.tif
> -------rw-    1 tracy Market 971432 Feb 18 11:24 28034 copy.tif
> 
> The Samba machine is RH7.1, running Samba 2.0.10-2. In the smb.conf I have 
> set 'create mode' and 'directory mode' to 776.
> 
> What am I missing here?
> 
> Thanks in advance for any help.
> Wayne
> 
> 
> 

-- 
G�rard Perreault
[EMAIL PROTECTED]

Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com

Reply via email to