oplock break

Jaroslav Jirásek jarda na egerius.cz
Čtvrtek Srpen 5 11:02:21 CEST 1999


mam redhat 6.0, sambu 2.0.5a, toto se mi obcas objevi v logu uzivatele:

[1999/08/05 10:45:44, 0] smbd/oplock.c:oplock_break(905)
  oplock_break resend
[1999/08/05 10:45:54, 0] smbd/oplock.c:oplock_break(905)
  oplock_break resend
[1999/08/05 10:46:04, 0] smbd/oplock.c:oplock_break(905)
  oplock_break resend
[1999/08/05 10:46:14, 0] smbd/oplock.c:oplock_break(922)
  oplock_break: receive_smb timed out after 30 seconds.
  oplock_break failed for file ORSOFT/SOUBORY/ORTSAV02.RLT (dev = 901, inode
= 332274).
[1999/08/05 10:46:14, 0] smbd/oplock.c:oplock_break(992)
  oplock_break: client failure in break - shutting down this smbd.

pote mu ten ucetni program ztuhne. Uz nekolik dni nad tim badam,
objevil jsem pouze toto v smb.conf.5:

oplock break wait time (G)
This is a tuning parameter added due to bugs in both Windows 9x and WinNT.
If Samba responds to a client too quickly when that client issues an SMB
that can cause an oplock break request, then the client redirector can fail
and not respond to the break request. This tuning parameter (which is set in
milliseconds) is the amount of time Samba will wait before sending an oplock
break request to such (broken) clients.
Default: oplock break wait time = 10

Nevite, jak tuto chybu odstranit?

Dik, Jarda






Další informace o konferenci Linux