Em Dom 08 Jul 2001 12:26, Luis Carlos escreveu:
> Ol�....
> Amigos ainda nao consegui resolver o meu problema no Samba vers�o 2.2.0,
> o que acontece eh o seguinte, tenho um servidor CL6.0 com um
> compartilhamento feito pelo Samba para uma pasta onde temos um
softwaroplock break wait time (G)
Poxa, est� tudo escrito na documenta��o:
Retirado de
http://us2.samba.org/samba/docs/man/smb.conf.5.html#OPLOCKBREAKWAITTIME
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 network client 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.
DO NOT CHANGE THIS PARAMETER UNLESS YOU HAVE READ AND UNDERSTOOD THE SAMBA
OPLOCK CODE.
Default: oplock break wait time = 0oplock contention limit (S)
This is a very advanced smbd(8) tuning option to improve the efficiency of
the granting of oplocks under multiple client contention for the same file.
In brief it specifies a number, which causes smbd not to grant an oplock even
when requested if the approximate number of clients contending for an oplock
on the same file goes over this limit. This causes smbd to behave in a
similar way to Windows NT.
DO NOT CHANGE THIS PARAMETER UNLESS YOU HAVE READ AND UNDERSTOOD THE SAMBA
OPLOCK CODE.
Default: oplock contention limit = 2oplocks (S)
This boolean option tells smbd whether to issue oplocks (opportunistic locks)
to file open requests on this share. The oplock code can dramatically
(approx. 30% or more) improve the speed of access to files on Samba servers.
It allows the clients to aggressively cache files locally and you may want to
disable this option for unreliable network environments (it is turned on by
default in Windows NT Servers). For more information see the file Speed.txt
in the Samba docs/ directory.
Oplocks may be selectively turned off on certain files with a share. See the
veto oplock files parameter. On some systems oplocks are recognized by the
underlying operating system. This allows data synchronization between all
access to oplocked files, whether it be via Samba or NFS or a local UNIX
process. See the kernel oplocks parameter for details.
See also the kernel oplocks and level2 oplocks parameters.
Default: oplocks = yes
Assinantes em 08/07/2001: 2258
Mensagens recebidas desde 07/01/1999: 121959
Historico e [des]cadastramento: http://linux-br.conectiva.com.br
Assuntos administrativos e problemas com a lista:
mailto:[EMAIL PROTECTED]
