samba - Oct 2000 - File permissions problem

Hi All,
	I was hoping someone can help me with a small problem. I have a 5 user
Samba network running on Red Hat 6. One user is set up to have root
equivalence but he only has read-only access to files created by other users
(its also fair to say that the other users only have read-only access to
each others files). I have tried messing around with the Linux permissions
on the files concerned (in a shared data directory), put all the users in
the same group, messed around with the share masks in the smb.conf file but
I still cant crack it, any idea what I'm missing/doing wrong? The Linux box
is the only server on the network, the rest of the machines are 95/98, I
have user level security turned on.

Many thanks

Ash

Attached is the contents of the smb.conf file (apologies for the length of
this post)

[global]

# workgroup = NT-Domain-Name or Workgroup-Name
   workgroup = CCL

# server string is the equivalent of the NT Description field
   server string = Samba Server

# This option is important for security. It allows you to restrict
# connections to machines which are on your local network. The
# following example restricts access to two C class networks and
# the "loopback" interface. For more examples of the syntax see
# the smb.conf man page
;   hosts allow = 192.168.1. 192.168.2. 127.

    hosts allow = 192.168.0. 127.

# if you want to automatically load your printer list rather
# than setting them up individually then you'll need this
   printcap name = /etc/printcap
   load printers = yes

# It should not be necessary to spell out the print system type unless
# yours is non-standard. Currently supported print systems include:
# bsd, sysv, plp, lprng, aix, hpux, qnx
;   printing = bsd

# Uncomment this if you want a guest account, you must add this to
/etc/passwd
# otherwise the user "nobody" is used
;  guest account = pcguest

# this tells Samba to use a separate log file for each machine
# that connects
;   log file = /var/log/samba/log.%m

# Put a capping on the size of the log files (in Kb).
;   max log size = 50

# Security mode. Most people will want user level security. See
# security_level.txt for details.
   security = user

# Use password server option only with security = server
;   password server = <NT-Server-Name>

# Password Level allows matching of _n_ characters of the password for
# all combinations of upper and lower case.
;  password level = 8
;  username level = 8

# You may wish to use password encryption. Please read
# ENCRYPTION.txt, Win95.txt and WinNT.txt in the Samba documentation.
# Do not enable this option unless you have read those documents
;  encrypt passwords = yes
;  smb passwd file = /etc/smbpasswd

# Unix users can map to different SMB User names
;  username map = /etc/smbusers

# Using the following line enables you to customise your configuration
# on a per machine basis. The %m gets replaced with the netbios name
# of the machine that is connecting
;   include = /etc/smb.conf.%m

# Most people will find that this option gives better performance.
# See speed.txt and the manual pages for details
   socket options = TCP_NODELAY

# Configure Samba to use multiple interfaces
# If you have multiple network interfaces then you must list them
# here. See the man page for details.
;   interfaces = 192.168.12.2/24 192.168.13.2/24

    interfaces = 192.168.0.1/255.255.255.0

# Configure remote browse list synchronisation here
#  request announcement to, or browse list sync from:
#	a specific host or from / to a whole subnet (see below)
;   remote browse sync = 192.168.3.25 192.168.5.255

    remote browse sync = 192.168.0.255

# Cause this host to announce itself to local subnets here
;   remote announce = 192.168.1.255 192.168.2.44

    remote announce = 192.168.0.255

# Browser Control Options:
# set local master to no if you don't want Samba to become a master
# browser on your network. Otherwise the normal election rules apply
   local master = yes

# OS Level determines the precedence of this server in master browser
# elections. The default value should be reasonable
   os level = 33

# Domain Master specifies Samba to be the Domain Master Browser. This
# allows Samba to collate browse lists between subnets. Don't use this
# if you already have a Windows NT domain controller doing this job
   domain master = yes

# Preferred Master causes Samba to force a local browser election on startup
# and gives it a slightly higher chance of winning the election
   preferred master = yes

# Use only if you have an NT server on your network that has been
# configured at install time to be a primary domain controller.
;   domain controller = <NT-Domain-Controller-SMBName>

# Enable this if you want Samba to be a domain logon server for
# Windows95 workstations.
   domain logons = yes

# if you enable domain logons then you may want a per-machine or
# per user logon script
# run a specific logon batch file per workstation (machine)
;   logon script = %m.bat
# run a specific logon batch file per username
;   logon script = %U.bat

# Where to store roving profiles (only for Win95 and WinNT)
#        %L substitutes for this servers netbios name, %U is username
#        You must uncomment the [Profiles] share below
;   logon path = \\%L\Profiles\%U

# All NetBIOS names must be resolved to IP Addresses
# 'Name Resolve Order' allows the named resolution mechanism to be
specified
# the default order is "host lmhosts wins bcast". "host"
means use the unix
# system gethostbyname() function call that will use either /etc/hosts OR
# DNS or NIS depending on the settings of /etc/host.config,
/etc/nsswitch.conf
# and the /etc/resolv.conf file. "host" therefore is system
configuration
# dependant. This parameter is most often of use to prevent DNS lookups
# in order to resolve NetBIOS names to IP Addresses. Use with care!
# The example below excludes use of name resolution for machines that are
NOT
# on the local network segment
# - OR - are not deliberately to be known via lmhosts or via WINS.
; name resolve order = wins lmhosts bcast

  name resolve order = hosts

# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable it's WINS
Server
   wins support = no

# WINS Server - Tells the NMBD components of Samba to be a WINS Client
#	Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
;   wins server = w.x.y.z

# WINS Proxy - Tells Samba to answer name resolution queries on
# behalf of a non WINS capable client, for this to work there must be
# at least one	WINS Server on the network. The default is NO.
   wins proxy = no

# DNS Proxy - tells Samba whether or not to try to resolve NetBIOS names
# via DNS nslookups. The built-in default for versions 1.9.17 is yes,
# this has been changed in version 1.9.18 to no.
   dns proxy = no

# Case Preservation can be handy - system default is _no_
# NOTE: These can be set on a per share basis
  preserve case = no
  short preserve case = no

# Default case is normally upper case for all DOS files
  default case = lower

# Be very careful with case sensitivity - it can break things!
  case sensitive = no

#============================ Share Definitions
=============================[homes]
   comment = Home Directories
   browseable = no
   writable = yes
   create mask = 2777

[accounts]
    comment = Accounts data directory
    path = /home/accounts
    valid users = andy ash pat
    public = yes
    writeable = yes
    printable = no
    read only = no
    create mask = 2777

[data]
   comment = Shared data directory
   path = /home/data
   public = yes
   writeable = yes
   printable = no
   read only = no
   create mask = 2777

[home]
   comment = root to home directories
   path = /home
   valid users = andy ash
   public = yes
   writeable = yes
   printable = no
   read only = no
   create mask = 2777

[cdrom]
   comment = CDROM drive
   path = /mnt/cdrom
   public = yes
   printable = no
   read only = yes

# NOTE: If you have a BSD-style print system there is no need to
# specifically define each individual printer
[printers]
   comment = All Printers
   path = /var/spool/samba
   browseable = no
   public = yes; to allow user 'guest account' to print
   guest ok = no
   writable = no
   printable = yes

I have a Redhat 7.3 system running Samba server for Windows98 networked
users. These users are registered users on the Linux box, using encrypted
passwords mirrored in Samba's password list. These users need to have file
ownership for existing and new files edited on their Windows PC's. To allow
this, I've made the following mods:

in etc/profile:				umask 002
in each user's data directory:	chmod -r 7775

in "etc/samba/smb.conf" global settings section:
create mask = 7775
inherit permissions=yes
force create mode 0664


This allows proper file ownership, and I then set all files in each user's
directory to be "read only" to all users but its owner. It also allows
me to
assign other group permissions as is necessary without disrupting the
ownerships. Sometimes though, a user will copy a data file from their own
directory into another user's directory, with the intention of having the
file be "writable" by the 2nd user. However, the file continues to
hold the
original ownership, and is "read only" to the 2nd user, even though it
now
resides in the 2nd user's data directory.

I need to find the correct "chmod" command, or other method, to allow
these
special files to become writable. It needs to be via a one-time command or
script entered at the server, as these Windows users do not have access to a
Linux shell, only to their Samba network shares.

Any suggestions?
***********************
Thanks,
Mark S.

I have a Redhat 7.3 system running Samba server for Windows98 networked
users. These users are registered users on the Linux box, using encrypted
passwords mirrored in Samba's password list. These users need to have file
ownership for existing and new files edited on their Windows PC's. To allow
this, I've made the following mods:

in etc/profile:				umask 002
in each user's data directory:	chmod -r 7775

in "etc/samba/smb.conf" global settings section:
create mask = 7775
inherit permissions=no
force create mode 0664


This allows proper file ownership, and I then set all files in each user's
directory to be "read only" to all users but its owner. It also allows
me to
assign other group permissions as is necessary without disrupting the
ownerships. Sometimes though, a user will copy a data file from their own
directory into another user's directory, with the intention of having the
file be "writable" by the 2nd user. However, the file continues to
hold the
original ownership, and is "read only" to the 2nd user, even though it
now
resides in the 2nd user's data directory.

I need to find the correct "chmod" command, or other method, to allow
these
special files to become writable. It needs to be via a one-time command or
script entered at the server, as these Windows users do not have access to a
Linux shell, only to their Samba network shares.

I've also tried "inherit permissions=yes" but it did not correct
the
problem.

Any suggestions?
***********************
Thanks,
Mark S.