[Samba] Fw: Files left open

[Jack Gostl]

I believe I already have them off. Here is what my config file looks like 
now.  ('vocab' is the culpit share)

[global]
        workgroup = ARGOS-SAMBA
        encrypt passwords = Yes
        netbios name = aix433
        posix locking=no
        oplocks = no
        level2 oplocks = no
[vocab]
        comment = Vocabulary
        path = /records/vocab
        writeable = Yes
        browsable = Yes
        posix locking = no
        oplocks = no
        level2 oplocks = no

----- Original Message ----- 
From: "Jeremy Allison" <jra at samba.org>
To: "Jack Gostl" <gostl at argoscomp.com>
Cc: "Samba" <samba at lists.samba.org>
Sent: Monday, July 31, 2006 12:11 PM
Subject: Re: [Samba] Fw: Files left open


> On Mon, Jul 31, 2006 at 11:59:00AM -0400, Jack Gostl wrote:
>> I'm still stuggling with files left open. My app is a Dialogic 
>> application
>> on a Win2K box. The host is running AIX 5.1 ML2 and samba 3.0.23a. 
>> Whenever
>> my PC app speaks a prompt stored on the AIX box, the file stays open.
>> smbstatus, fuser and lsof all agree the file is open.
>>
>> All other apps that I've tried, Winzip, pkzip, vi, etc., behave properly.
>>
>> I just can't believe this is a samba issue, but the vendor, Dialogic, is
>> stonewalling on their side. They keep saying "It doesn't happen with 
>> local
>> files, so if it happens in a share, it isn't our problem."
>>
>> So I'm kind of stuck, and looking for advice.
>
> Try turning off oplocks to see if that changes the behaviour.
> Client redirectors tend to leave batch oplocked files open without telling
> the application.
>
> Jeremy.
>