Your message dated Sat, 25 Apr 2009 07:35:17 +0200
with message-id <[email protected]>
and subject line Re: [Pkg-samba-maint] Bug#525321: Bug#525321: Bug#525321:
samba: "force create mode" option no longer works
has caused the Debian Bug report #525321,
regarding samba: "force create mode" option no longer works
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
525321: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=525321
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: samba
Version: 2:3.2.5-4lenny2
Severity: normal
After upgrading to lenny (from etch) it seems that the "force create mode"
option no longer works. However, if I downgrade samba to 3.0.24-6etch10 the
option works as it should. Here's an example:
nikos...@kubuntubox:~$ touch testfile; chmod 600 testfile
nikos...@kubuntubox:~$ mv testfile /mnt/smb/archives/
teh-server:~# ls -l /mnt/md1/archives/testfile
-rw------- 1 samba samba 0 2009-04-23 11:23 /mnt/md1/archives/testfile
When using the older version of samba, the permissions of that file would
have been -rw-rw-r-- which is consistent with what I have in my config file.
The relevant bits from my /etc/samba/smb.conf:
[global]
----snip----
force user = samba
force group = samba
directory mask = 0775
create mask = 0664
force create mode = 0664
force directory mode = 0775
browseable = yes
guest ok = yes
-- System Information:
Debian Release: 5.0.1
APT prefers oldstable
APT policy: (500, 'oldstable'), (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 2.6.26-2-686 (SMP w/1 CPU core)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages samba depends on:
ii adduser 3.110 add and remove users and groups
ii debconf [debcon 1.5.24 Debian configuration management sy
ii libacl1 2.2.47-2 Access control list shared library
ii libattr1 1:2.4.43-2 Extended attribute shared library
ii libc6 2.7-18 GNU C Library: Shared libraries
ii libcomerr2 1.41.3-1 common error description library
ii libcups2 1.3.8-1lenny5 Common UNIX Printing System(tm) -
ii libgnutls26 2.4.2-6+lenny1 the GNU TLS library - runtime libr
ii libkrb53 1.6.dfsg.4~beta1-5lenny1 MIT Kerberos runtime libraries
ii libldap-2.4-2 2.4.11-1 OpenLDAP libraries
ii libpam-modules 1.0.1-5+lenny1 Pluggable Authentication Modules f
ii libpam-runtime 1.0.1-5+lenny1 Runtime support for the PAM librar
ii libpam0g 1.0.1-5+lenny1 Pluggable Authentication Modules l
ii libpopt0 1.14-4 lib for parsing cmdline parameters
ii libtalloc1 1.2.0~git20080616-1 hierarchical pool based memory all
ii libwbclient0 2:3.2.5-4lenny2 client library for interfacing wit
ii logrotate 3.7.1-5 Log rotation utility
ii lsb-base 3.2-20 Linux Standard Base 3.2 init scrip
ii procps 1:3.2.7-11 /proc file system utilities
ii samba-common 2:3.2.5-4lenny2 Samba common files used by both th
ii update-inetd 4.31 inetd configuration file updater
ii zlib1g 1:1.2.3.3.dfsg-12 compression library - runtime
samba recommends no packages.
Versions of packages samba suggests:
pn ldb-tools <none> (no description available)
ii openbsd-inetd [inet-superse 0.20080125-2 The OpenBSD Internet Superserver
pn smbldap-tools <none> (no description available)
-- debconf information:
samba/run_mode: daemons
samba/tdbsam: false
samba/generate_smbpasswd: false
--- End Message ---
--- Begin Message ---
Quoting Nick Nobody ([email protected]):
> That makes sense, I recall reading that unix extensions (or something
> that has to do with that setting) for the etch version of samba was
> broken (it also explains some errors I'd get when doing certain file
> operations). I disabled "unix extensions" with version 2:3.2.5-4lenny2
> and sure enough, it works.
>
> Thanks for your help and sorry for wasting your time,
No problem. In your case it is understandable that you were puzzled as
the behaviour changed....but as I was suspecting the behaviour changed
*in the right way*.
Thanks Steve, for bringing useful comments and finding the right
keywords (Unix extensions). I think this bug can be closed now.
signature.asc
Description: Digital signature
--- End Message ---
