summaryrefslogtreecommitdiff
path: root/docs/docbook/smbdotconf/misc/dosfiletimeresolution.xml
blob: 600294d4428157103070a86af7d9bd34f04aae8a (plain)
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
<samba:parameter name="dos filetime resolution"
		 context="S"
		 xmlns:samba="http://samba.org/common">
<listitem>
	<para>Under the DOS and Windows FAT filesystem, the finest 
	granularity on time resolution is two seconds. Setting this parameter 
	for a share causes Samba to round the reported time down to the 
	nearest two second boundary when a query call that requires one second 
	resolution is made to <citerefentry><refentrytitle>smbd</refentrytitle>
	<manvolnum>8</manvolnum></citerefentry>.</para>

	<para>This option is mainly used as a compatibility option for Visual 
	C++ when used against Samba shares. If oplocks are enabled on a 
	share, Visual C++ uses two different time reading calls to check if a 
	file has changed since it was last read. One of these calls uses a
	one-second granularity, the other uses a two second granularity. As
	the two second call rounds any odd second down, then if the file has a
	timestamp of an odd number of seconds then the two timestamps will not
	match and Visual C++ will keep reporting the file has changed. Setting
	this option causes the two timestamps to match, and Visual C++ is
	happy.</para>

	<para>Default: <command moreinfo="none">dos filetime resolution = no</command></para>
</listitem>
</samba:parameter>