| Line | |
|---|
| 1 | <samba:parameter name="dos filetime resolution"
|
|---|
| 2 | context="S"
|
|---|
| 3 | type="boolean"
|
|---|
| 4 | xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
|
|---|
| 5 | <description>
|
|---|
| 6 | <para>Under the DOS and Windows FAT filesystem, the finest
|
|---|
| 7 | granularity on time resolution is two seconds. Setting this parameter
|
|---|
| 8 | for a share causes Samba to round the reported time down to the
|
|---|
| 9 | nearest two second boundary when a query call that requires one second
|
|---|
| 10 | resolution is made to <citerefentry><refentrytitle>smbd</refentrytitle>
|
|---|
| 11 | <manvolnum>8</manvolnum></citerefentry>.</para>
|
|---|
| 12 |
|
|---|
| 13 | <para>This option is mainly used as a compatibility option for Visual
|
|---|
| 14 | C++ when used against Samba shares. If oplocks are enabled on a
|
|---|
| 15 | share, Visual C++ uses two different time reading calls to check if a
|
|---|
| 16 | file has changed since it was last read. One of these calls uses a
|
|---|
| 17 | one-second granularity, the other uses a two second granularity. As
|
|---|
| 18 | the two second call rounds any odd second down, then if the file has a
|
|---|
| 19 | timestamp of an odd number of seconds then the two timestamps will not
|
|---|
| 20 | match and Visual C++ will keep reporting the file has changed. Setting
|
|---|
| 21 | this option causes the two timestamps to match, and Visual C++ is
|
|---|
| 22 | happy.</para>
|
|---|
| 23 | </description>
|
|---|
| 24 | <value type="default">no</value>
|
|---|
| 25 | </samba:parameter>
|
|---|
Note:
See
TracBrowser
for help on using the repository browser.
