|Main Archive Page > Month Archives > samba-users archives|
On Wed, Aug 04, 2010 at 10:52:20AM +0200, Thijs van der Kraan wrote:
> The parameters 'force create mode' and 'force directory mode' have no effect when the option 'unix extensions' is active. The documentation does not report any interaction between the unix extensions and the forced modes, so I'm assuming it's a bug.I'd like to know if it is a known bug ?Has it been solved, if so in which version ?
> My server runs Debian lenny, 2.6.26-2-amd64
> dpkg -l |grep smbii libsmbclient 2:3.2.5-4lenny12 shared library that allows applications to talk to SMB/CIFS seii libsmbios2 2.0.3.dfsg-1 Provide access to (SM)BIOS information -- dynamic libraryii smbclient 2:3.2.5-4lenny12 a LanManager-like simple client for Unixii smbfs 2:3.2.5-4lenny12 mount and umount commands for the smbfs (for kernels >= than 2
> My client run Ubuntu Lucid, 2.6.32-24-genericpkg -l |grep smbii libsmbclient 2:3.4.7~dfsg-1ubuntu3 shared library for communication with SMB/CIii python-smbc 1.0.6-0ubuntu3 Python bindings for Samba clients (libsmbcliii smbclient 2:3.4.7~dfsg-1ubuntu3 command-line SMB/CIFS clients for Unixii smbfs 2:3.4.7~dfsg-1ubuntu3 Samba file system utilities
Check out the parameters "force security mode" and "force directory security mode"
which you will also need when using unix extensions. Remember that the CIFSFS client
code often creates a file then sets the mode afterwards, in two operations, not one.
-- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba