Hey list,
I'm seeing some strange behavior on a Samba server on a Fedora Core 2
system. What's happening is that a user, with full access to a folder,
will delete a file through Windows explorer. The file will disappear,
just like it was deleted. However, upon a refresh, the file is back
again. Thus far, the only workaround I've found is to change the user to
be the owner of the file/folder they're trying to delete. With an office
full of people using and sharing files/folders, this is not an efficient
way to go about doing things.
Our shares are set up to give access by group, and these users all have
full access to the folders they're trying to delete files out of. For
some reason though, the file isn't being deleted.
I've tried this on 2 file servers now, just to be sure. One is a Fedora
Core 2 system running Samba 3.0.10-1.fc2, and the other is running
Fedora Core 3 running Samba 3.0.11. Both systems show the same thing.
All workstations connecting to these systems are running Windows XP Home
with SP2 installed.
The smb.conf file is quite simple, and looks like this:
**********************************************************************************************
[global]
workgroup = Production
server string = Fileserver
printcap name = /etc/printcap
load printers = yes
cups options = raw
log file = /var/log/samba/%m.log
max log size = 50
security = user
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
dns proxy = no
#============================ Share Definitions
=============================[homes]
comment = Home Directories
browseable = no
writable = yes
valid users = %S
create mode = 0600
directory mode = 0600
[printers]
comment = All Printers
path = /var/spool/samba
browseable = no
# Set public = yes to allow user 'guest account' to print
guest ok = no
writable = no
printable = yes
[Share1]
comment = Share1
path = /folder1
valid users = @accounting,@sales,@dataentry,@operations
public = no
writable = yes
printable = no
create mask = 3660
directory mask = 3770
**********************************************************************************************
Any suggestions on why this is happening?
Thanks,
Brandon