Hmm, performance. How drastic is the lost of performance if i disable oplocks. And isn't it a problem, when i disable them and some tries to open an already opened file?
Michael
At 11:41 26.01.2003 -0500, you wrote:
Read about oplocks in the samba documentation. SWAT might be nice.
Disable oplocks on your samba server, if you don't mind the performance hit.
Oplocks are fine when they work, but a source of file corruption when they
fail.
"shutting down this smbd" just means that the daemon serving that connection
is closing. This is good.
Joel
On Sun, Jan 26, 2003 at 05:27:21PM +0100, Michael Paarmann wrote:
> Dear list!
>
> I'm very confused and it would be very nic, if someone can help me.
>
> I've installed a Sambaserver (2.2.3a) based on SuSE Linux 8.0. Nealy 40
> clients with Windows 98, Windows 2000 or Windows XP Pro are working with
> this Samba. Now my problem:
> Sometimes the client are crashing down and i see in /var/log/warn something
> like: oplock_break: client failure in break - shutting down this smbd.
> before they crash.
>
> I've searched Google and so on, but i haven't find an acceptable solution
> for this. But i've seen, thatr a lot people have this problem too.
>
> So, does anyone have an answer or a tip ?!
>
> Thanks in advance.
>
> Michael
--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba
squIT - Individuelle IT-L�sungen
Michael Paarmann
Saturnweg 23
D- 45478 M�lheim an der Ruhr
Fon:
Mobil:
Fax:
E-Mail: [EMAIL PROTECTED]
M-Mail: [EMAIL PROTECTED]
Web: http://www.squIT.de
______________________________________
