samba - Feb 1998 - Oplock question/problem ???

You wrote:
|                                    The Win95 redirector has a nasty 
| habit of keeping batch oplocked files open long after the application
| has actually closed the file. WinNT seems to suffer less than this.
[snip]
| Maybe I should add a 'break oplock after XX minutes
| of inactivity parameter'..... Hmmmmm. That might make
| some things a lot slower though.

  If it's limited to batch oplocks on non-.BAT files, you might
consider writing a very specific oplock-discarder just for that
case.
  I'm assuming, of course, that only win95 makes this particular
error and that it will go away eventually. Alas, one former
employer tended to do just the opposite: publicize useful bugs
for general customer use (:-0)

--dave (those guys aren't in business any more) c-b
--
David Collier-Brown,  | Always do right. This will gratify some people
185 Ellerslie Ave.,   | and astonish the rest.        -- Mark Twain
Willowdale, Ontario   | davecb@hobbes.ss.org, canada.sun.com
M2N 1Y3. 416-223-8968 | http://java.science.yorku.ca/~davecb

> I've done a "man smb.conf", Yes, oplocks can be turned off in
a per share
> basis, but shutting off oplocks to all the individual shares that I would
> have to would be more of a hassle than just doing it globally.  At the
> moment it's the only question/problem I have using Samba and I
don't feel
> it's a critical one at that since everything else runs like a dream.  I
> definitely wouldn't stop using Samba for something this trivial. 
I'll just
> do without the oplocks till I can find a work around for my problem.
You're right: there's no need to stop using Samba only because of
this small problem. Besides, before 1.9.18 you didn't have OpLocks so
probably your users won't even notice that OpLocks are turned off :-)

See ya!

E.-

-- 

Eloy A. Paris
Information Technology Department
Rockwell Automation de Venezuela
Telephone: +58-2-9432311 Fax: +58-2-9431645