summaryrefslogtreecommitdiff
path: root/FreeFileSync/Build/Help/html/expert-settings.html
blob: d430be4eb1d4ae5220952581e0cca3748f20c3da (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
87
88
89
90
91
92
93
94
95

<!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">
			&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;<br>
			&lt;FreeFileSync XmlType=&quot;GLOBAL&quot;&gt;<br>
			&nbsp;&nbsp;&nbsp;&nbsp;&lt;General&gt;<br>
			&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;<b>FileTimeTolerance</b> Seconds=&quot;2&quot;/&gt;<br>
			&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;<b>FolderAccessTimeout</b> Seconds=&quot;20&quot;/&gt;<br>
			&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;<b>RunWithBackgroundPriority</b> Enabled=&quot;false&quot;/&gt;<br>
			&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;<b>LockDirectoriesDuringSync</b> Enabled=&quot;true&quot;/&gt;<br>
			&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;<b>VerifyCopiedFiles</b> Enabled=&quot;false&quot;/&gt;<br>
			&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;<b>LastSyncsLogSizeMax</b> Bytes=&quot;100000&quot;/&gt;<br>
			&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;<b>NotificationSound</b> SyncComplete=&quot;harp.wav&quot;/&gt;
		</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 only with a 2-second precision.
	</p>

	<p>
		<b>FolderAccessTimeout:</b><br>
		When testing if a particular folder path exists FreeFileSync will time out
		after the specified number of seconds if the operating system does not respond (e.g. non-reachable network share).
	</p>

	<p>
		<b>RunWithBackgroundPriority:</b><br>
		While synchronization is running, other applications that 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>).
		The lock files are only recognized by FreeFileSync and make sure that only a single instance 
		can read and write a shared folder while other instances are queued to wait.
		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. Additionally corruption may be 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>
	
	<p>
		<b>NotificationSound:</b><br>
		Select a sound file from the FreeFileSync installation directory to be played after synchronization. Set an empty name if no sound should be played.
	</p>	
</body>
</html>
bgstack15