AW: Samba 2.2.2 oplock problem

[Andreas Moroder]

Hello Jeremy,

this explains many things.
Few days ago I maed a post with the title "strange message in log file and 
files automaticaly closed".
We had a application ( Clipper / DOS ) that did hang and I found a message 
from the pam_auth in the logs.
Probably smbd was killed because of this contention problem and windows did 
reconnect so we did get the pam message ( because we use plaintext ( argh ) 
password ).

...
two minutes later
...

I did now grep the logs and did find many panic messages in different logs, 
but all concentrated on two times. All this PC try to use the same database 
file.

This panics was all from 26.11. The night from 26 to 27 we installed a new 
version and the last two days I got no panic.

I will try the latest cvs as soon as possible.

Thanks

Andreas



> -----Ursprüngliche Nachricht-----
> Von:	Jeremy Allison [SMTP:jra at samba.org]
> Gesendet am:	Mittwoch, 28. November 2001 00:10
> An:	Deimert, Daniel
> Cc:	'jra at samba.org'; samba-technical at samba.org; Andreas Moroder
> Betreff:	Re: Samba 2.2.2 oplock problem
>
> Hi all,
>
> 	I think I've finally worked out what is causing the panic
> error messages. This is the :
>
> open_mode_check: Existant process XXXX left active oplock.
>
> messages that people have mainly been seeing on Solaris (but
> occasionally on Linux also).
>
> ..... ( it's so long so I cutted it )