Same exact failure with
Linux 2.0.38
Linux 2.2.20
Linux 2.4.18
SunOS 5.6
I'll have to let you know Tuesday if it fails with just any old executable... but I'd
expect it
would.
Rich B
----- Original Message -----
From: "Jeremy Allison" <[EMAIL PROTECTED]>
To: "Richard Bollinger" <[EMAIL PROTECTED]>
Cc: "Jeremy Allison" <[EMAIL PROTECTED]>; "Samba Technical" <[EMAIL PROTECTED]>
Sent: Friday, May 24, 2002 6:58 PM
Subject: Re: Thanks for fixing oplock.c for Linux 2.0 in 2_2 CVS
On Fri, May 24, 2002 at 02:05:12PM -0400, Richard Bollinger wrote:
> OK... time for a brain flush and refill...
>
> I went back and verified my test conditions and determined that the same failure can
>be
demonstrated
> with every server platform we own running Samba 2.X with oplocks enabled and with a
>Win98
client.
> Here's the setup:
>
> On Win98 client:
> net use i: \\server\share1
>
> On Server:
> smbd instance goes away by dead time exceeded or with kill command
>
> On Win98 client:
> net use j: \\server\share2
> j:
> cd netbench
> netbench.exe <<<--- here's where we get the oplock freeze for 30
>seconds
>
> I can send you a copy of the netbench directory off list if you need it. I suspect
>the same
failure
> will happen for any DOS executable.
What is the Linux kernel version you are running ? Can you confirm it happens
with any DOS executable and I'll then try and reproduce the problem.
Thanks,
Jeremy.
