|
Last change
on this file was 745, checked in by Silvan Scherrer, 13 years ago |
|
Samba Server: updated trunk to 3.6.0
|
|
File size:
1.1 KB
|
| Line | |
|---|
| 1 | <samba:parameter name="ctdb locktime warn threshold"
|
|---|
| 2 | context="G"
|
|---|
| 3 | type="integer"
|
|---|
| 4 | advanced="1"
|
|---|
| 5 | xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
|
|---|
| 6 | <description>
|
|---|
| 7 |
|
|---|
| 8 | <para>
|
|---|
| 9 | In a cluster environment using Samba and ctdb it is critical
|
|---|
| 10 | that locks on central ctdb-hosted databases like locking.tdb
|
|---|
| 11 | are not held for long. With the current Samba architecture
|
|---|
| 12 | it happens that Samba takes a lock and while holding that
|
|---|
| 13 | lock makes file system calls into the shared cluster file
|
|---|
| 14 | system. This option makes Samba warn if it detects that it
|
|---|
| 15 | has held locks for the specified number of milliseconds. If
|
|---|
| 16 | this happens, <emphasis>smbd</emphasis> will emit a debug level 0
|
|---|
| 17 | message into its logs and potentially into syslog. The most likely
|
|---|
| 18 | reason for such a log message is that an operation of the cluster
|
|---|
| 19 | file system Samba exports is taking longer than expected.
|
|---|
| 20 | The messages are meant as a debugging aid for potential
|
|---|
| 21 | cluster problems.
|
|---|
| 22 | </para>
|
|---|
| 23 |
|
|---|
| 24 | <para>The default value of 0 disables this logging.</para>
|
|---|
| 25 |
|
|---|
| 26 | </description>
|
|---|
| 27 | <value type="default">0</value>
|
|---|
| 28 | </samba:parameter>
|
|---|
Note:
See
TracBrowser
for help on using the repository browser.
