blob: 67314a1946ccc9aab4f75a56976b7f848349df91 (
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
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
|
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<link rel="stylesheet" type="text/css" href="base.css" >
<title>Expert Settings</title>
</head>
<body>
<h1>Expert Settings</h1>
<p>
FreeFileSync has a number of special purpose settings that can only be accessed
directly via the global configuration file <span class="file-path">GlobalSettings.xml</span>.
Note that this file is read once when FreeFileSync starts and saved when it closes. Therefore apply changes only while FreeFileSync is not running. <br>
<br>
To locate this file on Windows enter <span class="command-line">%appdata%\FreeFileSync</span> in the Windows Explorer address bar or go to the FreeFileSync
installation folder if you are using the portable installation.
On Linux you can find the file in <span class="command-line">~/.FreeFileSync</span> for the Launchpad release and in the installation folder for the portable version.
On OS X go to <span class="command-line">~/Library/Application Support/FreeFileSync</span>.
</p>
<div class="box-outer"><div class="greybox"><div class="box-inner">
<div class="command-line">
<?xml version="1.0" encoding="UTF-8"?><br>
<FreeFileSync XmlType="GLOBAL"><br>
<Shared><br>
<<b>FileTimeTolerance</b> Seconds="2"/><br>
<<b>RunWithBackgroundPriority</b> Enabled="false"/><br>
<<b>LockDirectoriesDuringSync</b> Enabled="true"/><br>
<<b>VerifyCopiedFiles</b> Enabled="false"/><br>
<<b>LastSyncsLogSizeMax</b> Bytes="100000"/>
</div>
</div></div></div>
<br>
<p>
<b>FileTimeTolerance:</b><br>
By default file modification times
are allowed to have a 2 second difference while still being
considered equal. This is required by FAT/FAT32 file systems which
store file times with a 2 second precision only.<br>This setting
can also be used to simulate a "compare by file size",
ignoring last modification times:
Set tolerance to -1 which will be considered as an unlimited file time tolerance.
Changed files will then be detected as a
conflict (same date, different file size) and the
synchronization direction for conflicts can be used accordingly.
</p>
<p>
<b>RunWithBackgroundPriority:</b><br>
While synchronization is running, other applications which are accessing the same
data locations may experience a noticeable slowdown. Enable this
setting to lower FreeFileSync's resource consumption at the cost of a
significantly slower synchronization speed.
</p>
<p>
<b>LockDirectoriesDuringSync:</b><br>
In order to avoid race conditions of multiple FreeFileSync instances
writing to the same folder at the same time, synchronization tasks are serialized
with lock files (<span class="file-path">sync.ffs_lock</span>).
This is primarily intended for network synchronization scenarios where
multiple users may run FreeFileSync concurrently against a common network folder.
</p>
<p>
<b>VerifyCopiedFiles:</b><br>
If active, FreeFileSync will binary-compare source and target files after
copying and report verification errors. Note that this may double
file copy times and is no guarantee that data has not already been
corrupted prior to copying and corruption is not hidden by
deceptively reading valid data from various buffers in the
application and hardware stack.<br>
<a rel="nofollow" target="_blank" href="https://blogs.msdn.microsoft.com/oldnewthing/20120919-00/?p=6563/">Does
the CopyFile function verify that the data reached its final destination successfully?</a>
</p>
<p>
<b>LastSyncsLogSizeMax:</b><br>
The progress logs of the most recent synchronizations (for both GUI and batch jobs) are collected automatically in the file <span class="file-path">LastSyncs.log</span>.
The maximum size of this log file can be set here.
</p>
</body>
</html>
|
