redhat 9.0, read only files

[karmic]

Have a RH9 server that's working well, first server to go into production but there is one problem...

One user can access and changes a file, say an .xls file, and save it and close it. When a different user opens the file it comes up as read-only for the second user...

It's driving me nuts. Seems the server gives full rights to the file to the first user that grabs it and sets it read only for anybody else that tries to use it...

Thanks...

~ K.I.S.S - Don't make it any more complex than it has to be ~

 

[ericbrunson]

Are you using samba for windows file sharing?

 

[karmic]

Here's the samba.conf

[global]

# workgroup = NT-Domain-Name or Workgroup-Name
workgroup = changed for protection
netbios name = server

# server string is the equivalent of the NT Description field
server string = linux 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.

# 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, cups
printing = cups

# 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/%m.log

# 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.

# Use password server option only with security = server
# The argument list may include:
# password server = My_PDC_Name [My_BDC_Name] [My_Next_BDC_Name]
# or to auto-locate the domain controller/s
# password 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/samba/smbpasswd

# The following is needed to keep smbclient from spouting spurious errors
# when Samba is built with support for SSL.
; ssl CA certFile = /usr/share/ssl/certs/ca-bundle.crt

# The following are needed to allow password changing from Windows to
# update the Linux system password also.
# NOTE: Use these with 'encrypt passwords' and 'smb passwd file' above.
# NOTE2: You do NOT need these to allow workstations to change only
# the encrypted SMB passwords. They allow the Unix password
# to be kept in sync with the SMB password.
unix password sync = Yes
passwd program = /usr/bin/passwd %u
passwd chat = *New*password* %n\n *Retype*new*password* %n\n *passwd:*all*authentication*tokens*updated*successfully*

# You can use PAM's password change control flag for Samba. If
# enabled, then PAM will be used for password changes when requested
# by an SMB client instead of the program listed in passwd program.
# It should be possible to enable this without changing your passwd
# chat parameter for most setups.

pam password change = yes

# Unix users can map to different SMB User names
; username map = /etc/samba/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/samba/smb.conf.%m

# This parameter will control whether or not Samba should obey PAM's
# account and session management directives. The default behavior is
# to use PAM for clear text authentication only and to ignore any
# account or session management. Note that Samba always ignores PAM
# for authentication in the case of encrypt passwords = yes

obey pam restrictions = yes

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

# 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

# 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
# Cause this host to announce itself to local subnets here
; remote announce = 192.168.1.255 192.168.2.44

# 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 = no

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

# 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 = no

# 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 = no

# 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

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

# 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 = yes

# 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.
username map = /etc/samba/smbusers
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 = yes
writeable = yes
valid users = %S
create mode = 0664
directory mode = 0775
# If you want users samba doesn't recognize to be mapped to a guest user
; map to guest = bad user


# Un-comment the following and create the netlogon directory for Domain Logons
; [netlogon]
; comment = Network Logon Service
; path = /usr/local/samba/lib/netlogon
; guest ok = no
; writable = no
; share modes = no


# Un-comment the following to provide a specific roving profile share
# the default is to use the user's home directory
;[Profiles]
; path = /usr/local/samba/profiles
; browseable = no
; guest ok = 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
# Set public = yes to allow user 'guest account' to print
printable = yes

# This one is useful for people to share files
[tmp]
comment = Temporary file space
path = /tmp
read only = no
public = yes

# A publicly accessible directory, but read only, except for people in
# the "staff" group
;[public]
; comment = Public Stuff
; path = /home/samba
; public = yes
; writable = yes
; printable = no
; write list = @staff


[acad]
path = /data/acad
valid users = Blank on purpose
comment = autocad
writeable = yes


[alpha]
path = /data/alpha
valid users = Blank on purpose
comment = alpha
writeable = yes


[finance]
path = /data/finance
valid users = Blank on purpose
comment = finance
writeable = yes


[general]
path = /data/general
valid users = Blank on purpose
comment = general
writeable = yes

[pictures]
path = /data/pictures
valid users = Blank on purpose
comment = pictures
writeable = yes


[secure]
path = /data/secure
valid users = Blank on purpose
comment = secure
writeable = yes

[public]
comment = public
path = /data/public
writeable = yes
valid users = Blank on purpose

[plus]
oplocks = no
comment = plus
writeable = yes
share modes = no
public = yes
path = /data/plus






~ K.I.S.S - Don't make it any more complex than it has to be ~

 

[karmic]

Eric, if you mean that this is strictly a windows network, then yes. It's a mixed bag of 98, 2000 and xp... No linux clients as of yet...

Thanks.

~ K.I.S.S - Don't make it any more complex than it has to be ~

 

[zum]

Karmic,

I just put my first linux Fedora 2 file server into production running samba. I noticed the same problem. I haven't found a solution to the problem yet. What I am doing for the moment to work around the problem is I made a cronjob that goes off every 5 minutes that changes my files to the proper permissions. Hopefully someone will post a message with a proper way of fixing it.

Zum

 

[karmic]

hey zum... I hope so. I wanted to go with fedora C2 but I had already bought a promise raid controller and it wasn't compatible with core2. Works like a charm on 9.0 tho after hours of cursing and spitting at it



~ K.I.S.S - Don't make it any more complex than it has to be ~

 

[karmic]

Zum...

I'm still a noob with linux but after a little bit of research I tried changing the numerical security.

For the directory that you want users to have full access to, enter the following...

create mask = 666
directory mask = 666

I ran a few tests after the fact, and I can now edit/save files and not have them read only for the next user...

Let me know if it works.

~ K.I.S.S - Don't make it any more complex than it has to be ~

 

[thedaver]

Also,
man umask

http://www.surfinbox.com/hosting/

 

[karmic]

daver, I'm still of a noob at this, can you xplain a little?

Thanks.

~ K.I.S.S - Don't make it any more complex than it has to be ~