[Samba] Excel Read only file bug back on 3.0.23x?

[Roland Hordos]

Thanks Silas, I think I'll try that in the mean time, for .xls and .doc
files.  I really don't know how deep the problem goes, though -- could
two AutoCAD users overwrite each other's drafting files?!  Do you know
what level of logging is required to see this oplock behavior in action?
At level 3 I get open_file and close_normal_file with read and write =
Yes or No.

I am currently running this share with no oplocking at all (smbd.conf
entries below), when I think it's only Excel and Word docs that are
vulnerable.  This causes a lot of user activity to have to save to their
local hard drive, then move to the Share in explorer.  At least this
works consistently and I'm confident that no two users can overwrite
each other's open files directly.

Current Workaround Setup

strict locking = yes
oplocks = no
level2 oplocks = no

Roland;


-----Original Message-----
From: Silas Wind [mailto:swi at clipper-group.com]
Sent: Monday, October 30, 2006 3:09 PM
To: Roland Hordos
Cc: samba at lists.samba.org
Subject: RE: [Samba] Excel Read only file bug back on 3.0.23x?


Hi

This is a "workaround", not a solution, if you want the Excel timestamp
feature enabled .

add   veto oplock files = /*.xls/  for each share in smb.conf  SHARE
section !

Or you edit the XP / W2K reg database see Microsoft official site for
bug
http://support.microsoft.com/kb/324491

Best regards

Silas Wind



 

             "Roland Hordos"

             <rolandhordos at tun

             draeng.com>
To 
             Sent by:                  "Diego Julian Remolina"

             samba-bounces+swi         <diego.remolina at ibb.gatech.edu>,

             =clipper-group.co         "samba at lists.samba.org"

             m at lists.samba.org         <samba at lists.samba.org>

 
cc 
 

             30-10-2006 19:55
Subject 
                                       RE: [Samba] Excel Read only file

                                       bug back on 3.0.23x?

 

 

 

 

 

 





Is your problem repeatable, for all users, and even on a fresh smb
restart?  For me it is not and this is the trickiest part of tracing
this bug.

I am desperately trying to resolve this as well.  Have not received any
replies from this board whatsoever.  Currently re-visiting every
parameter and samba default setting change across releases.  Good luck
and please post any results.

thanks, Roland;


-----Original Message-----
From: samba-bounces+rolandhordos=tundraeng.com at lists.samba.org
[mailto:samba-bounces+rolandhordos=tundraeng.com at lists.samba.org]On
Behalf Of Diego Julian Remolina
Sent: Monday, October 30, 2006 10:50 AM
To: samba at lists.samba.org
Subject: [Samba] Excel Read only file bug back on 3.0.23x?


Hi,

I believe that the BUG 2346 which was resolved in samba 3.0.14 has come
back in the 3.0.23 series.
Here is what I have noticed on two separate configurations. The samba
packages were built on each
machine using rpmbuild with the SRPMS provided for Fedora in the samba
web site.

Configuration 1.
Two machines running with RHEL4, samba 3.0.23b-1, drbd-0.7.21 protocol
C.
Kernel: 2.6.9-42.0.3.ELsmp

Configuration 2.
Two machines running with CentOS 4, samba 3.0.23c-4, drbd-0.7.21
protocol C.
Kernel: 2.6.9-42.0.2.ELsmp

I do not believe none of this is related to DRBD, but I mention it just
in case. The problem occurs
as follows:

1. User Alice opens an excel files owned by her, makes changes and saves
it.
2. User Bob opens the same file which Alice just saved and makes come
changes. When Bob saves the
file, he gets a warning that there is a problem and that changes could
not be saved, however changes
are saved.
3. Either Alice or Bob try to open the file and now it is a read only
file.

The only way anyone can save the file is if they first right click on it
and uncheck the read-only
checkbos prior to openning. However, the next time a different user
opens the file and saves it, the
problem comes back.

Are there any settings that can be changed in smb.conf to help prevent
this front happening? Is
anyone else experiencing this behaviour? Is it possible that the BUG
2346 came back?

Any help would be greatly appreciated.

Thanks,

Diego
--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba







--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba