mirror of
https://github.com/samba-team/samba.git
synced 2024-12-24 21:34:56 +03:00
80f648b169
This parameter adds complexity to our brlock implementation that I don't think is justified. Not a lot of complexity, but if we would want to really support it we'd need tests. Instead of doing those, I think removing the parameter is the better choice. Signed-off-by: Volker Lendecke <vl@samba.org> Reviewed-by: Jeremy Allison <jra@samba.org> Autobuild-User(master): Jeremy Allison <jra@samba.org> Autobuild-Date(master): Tue Jun 18 14:47:08 UTC 2019 on sn-devel-184
26 lines
1.0 KiB
XML
26 lines
1.0 KiB
XML
<samba:parameter name="blocking locks"
|
|
context="S"
|
|
type="boolean"
|
|
deprecated="1"
|
|
xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
|
|
<description>
|
|
<para>This parameter controls the behavior
|
|
of <citerefentry><refentrytitle>smbd</refentrytitle>
|
|
<manvolnum>8</manvolnum></citerefentry> when given a request by a client
|
|
to obtain a byte range lock on a region of an open file, and the
|
|
request has a time limit associated with it.</para>
|
|
|
|
<para>If this parameter is set and the lock range requested
|
|
cannot be immediately satisfied, samba will internally
|
|
queue the lock request, and periodically attempt to obtain
|
|
the lock until the timeout period expires.</para>
|
|
|
|
<para>If this parameter is set to <constant>no</constant>, then
|
|
samba will behave as previous versions of Samba would and
|
|
will fail the lock request immediately if the lock range
|
|
cannot be obtained.</para>
|
|
|
|
</description>
|
|
<value type="default">yes</value>
|
|
</samba:parameter>
|