File: locking.xml

package info (click to toggle)
samba 2%3A4.5.16%2Bdfsg-1%2Bdeb9u2
  • links: PTS, VCS
  • area: main
  • in suites: stretch
  • size: 119,272 kB
  • sloc: ansic: 1,353,805; xml: 120,204; python: 119,437; sh: 36,510; perl: 29,946; asm: 3,281; yacc: 2,332; cpp: 2,225; ada: 1,681; exp: 1,582; makefile: 1,365; pascal: 1,089; cs: 879; lex: 603; awk: 118; csh: 58; sed: 45
file content (29 lines) | stat: -rw-r--r-- 1,193 bytes parent folder | download | duplicates (8)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
<samba:parameter name="locking"
                 type="boolean"
                 context="S"
                 parm="1"
                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
<description>
	<para>This controls whether or not locking will be 
	performed by the server in response to lock requests from the 
	client.</para>

	<para>If <command moreinfo="none">locking = no</command>, all lock and unlock 
	requests will appear to succeed and all lock queries will report 
	that the file in question is available for locking.</para>

	<para>If <command moreinfo="none">locking = yes</command>, real locking will be performed 
	by the server.</para>

	<para>This option <emphasis>may</emphasis> be useful for read-only 
	filesystems which <emphasis>may</emphasis> not need locking (such as 
	CDROM drives), although setting this parameter of <constant>no</constant> 
	is not really recommended even in this case.</para>

	<para>Be careful about disabling locking either globally or in a 
	specific service, as lack of locking may result in data corruption. 
	You should never need to set this parameter.</para>
</description>

<value type="default">yes</value>
</samba:parameter>