[Samba] Excel "file may have been modified by another user since"with Samba 3.0.10

[David Landgren]

On Tue, 11 Jan 2005 11:24:00 -0500 (EST),
mrojava4 at eastgranby.k12.ct.us <mrojava4 at eastgranby.k12.ct.us> wrote:
> You may also want to read article 324491 at support.microsoft.com.  It
> applies to Excel 2002, but may be pertinent.

Oops, I got the exact message wrong, I'll restate it here so that web
searches can find it:

The file (foo.xls) may have been changed by another user since you last saved it

Thanks for the link, it may indeed relate to my problem. Anyway, in
the meantime, while poring over samba logs, I found aawful hack, and
that is to add

    veto oplock files = /*.xls/

to the [globals] section of smb.conf. That's pretty suboptimal, but it
gets the users off my back. There must be a better way.

Thanks,
David
 
> Mark Orenstein
> East Granby, CT School System
> 
> > Hello list,
> >
> > I am encountering a problem with Excel 2003 on Samba shares. If I open
> > an Excel file, edit a cell and then try to save it, I get a dialog box
> > with a "file may have been modified by another user since" message,
> > with the option to save a new copy, or overwrite the current file.
> > Subsequent saves don't exhibit this behaviour, it occurs only on the
> > first save after opening a file.
> >
> > This was using Samba 3.0.2. I went through the Changelogs and saw the
> > line in the 3.0.5 changes (Implement deferred open code to fix a bug
> > with Excel files on Samba shares.) and thought that this would do the
> > trick.
> >
> > I have built and rolled out 3.0.10, but the problem is still present.
> > The only file that smbstatus shows is as follows:
> >
> > Pid    DenyMode   Access      R/W        Oplock           Name
> > --------------------------------------------------------------
> > 15586  DENY_NONE  0x2019f     RDWR       EXCLUSIVE+BATCH
> > /home/d/david/a.xls   Tue Jan 11 15:02:14 2005
> >
> > I have tried the 'defer sharing violations' set to yes, set to no, but
> > that doesn't change anything. I assume I have to change something in
> > smb.conf but I don't know what it is.
> >
> > Thanks for any clues I can use,
> > David