SAMBA bestandspermissies

[Spearhead]

Ik zit met het volgende probleem:
Alle files worden standaard aangemaakt met permissies 0775, terwijl dat 0664 zou moeten zijn. Dat 'x' bitje geeft namelijk locking problemen, omdat samba er van uit gaat dat het executables betreft die door clients gecached mogen worden.

Tevens is het de bedoeling dat het setgid bitje op files en directories behouden blijft, anders kunnen mensen elkaars files niet openen.

Dit is een uittreksel van de config:

create mode = 0664
directory mode = 0775
inherit permissions = yes; en het sitgid bitje staat aan op de bovenliggende directory

Nu is het probleem: dit werkt niet Kennelijk heeft 'inherit permissions' voorrang boven 'create mode'.
Heeft iemand een idee hoe dit te fixen is ?

[cool_zero]

even een stukje man smb.conf:

code:

     inherit permissions (S)
          The permissions on new files and directories  are  normally  gov­
          erned  by   create  mask,   directory mask, force create mode and
          force directory mode but the boolean inherit permissions  parame­
          ter overrides this.
 
          New directories inherit the mode of the parent directory, includ­
          ing bits such as setgid.
 
          New files inherit their read/write bits from  the  parent  direc­
          tory. Their execute bits continue to be determined by map archive
          , map hidden and map system as usual.
 
          Note that the setuid bit is never set via inheritance  (the  code
          explicitly prohibits this).
 
          This can be particularly useful on large systems with many users,
          perhaps several thousand, to allow a single [homes] share  to  be
          used flexibly by each user.

en

code:

 map archive (S)
          This  controls whether the DOS archive attribute should be mapped
          to the UNIX owner execute bit. The DOS archive bit is set when  a
          file  has been modified since its last backup. One motivation for
          this option it to keep Samba/your PC  from  making  any  file  it
          touches  from  becoming  executable under UNIX. This can be quite
          annoying for shared source code, documents, etc...
 
          Note that this requires the create mask parameter to be set  such
          that  owner  execute  bit is not masked out (i.e. it must include
          100). See the parameter  create mask for details.
 
          Default: map archive = yes
 
    map hidden (S)
          This controls whether DOS style hidden files should be mapped  to
          the UNIX world execute bit.
 
          Note  that  this requires the create mask to be set such that the
          world execute bit is not masked out (i.e.  it must include  001).
          See the parameter  create mask for details.
 
          Default: map hidden = no
 
     map system (S)
          This  controls whether DOS style system files should be mapped to
          the UNIX group execute bit.
 
          Note that this requires the create mask to be set such  that  the
          group  execute bit is not masked out (i.e.  it must include 010).
          See the parameter  create mask for details.
 
          Default: map system = no

Volgens mij kunnen deze laatste drie opties wel wat voor je fixen., succes ermee

[Spearhead]

Dat zocht ik, ja. Thanks!