perso/syncthing-arm
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

gui, man: Update docs & translations

Browse Source
This commit is contained in:
Jakob Borg
2017-11-22 07:45:21 +01:00
parent a17d953334
commit b99e92bad7
18 changed files with 75 additions and 28 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
man/syncthing-faq.7
View File

@@ -1,6 +1,6 @@
.\" Man page generated from reStructuredText.
.
.TH "SYNCTHING-FAQ" "7" "September 08, 2017" "v0.14" "Syncthing"
.TH "SYNCTHING-FAQ" "7" "November 18, 2017" "v0.14" "Syncthing"
.SH NAME
syncthing-faq \- Frequently Asked Questions
.
@@ -211,6 +211,17 @@ everywhere else and we don\(aqt know which of the conflicting files is the "best
from the user point of view. Moreover, if there\(aqs something that automatically
causes a conflict on change you\(aqll end up with \fBsync\-conflict\-...sync\-conflict
\-...\-sync\-conflict\fP files.
.SS How do I serve a folder from a read only filesystem?
.sp
Syncthing requires a "folder marker" to indicate that the folder is present
and healthy. By default this is a directory called \fB\&.stfolder\fP that is
created by Syncthing when the folder is added. If this folder can\(aqt be
created (you are serving files from a CD or something) you can instead set
the advanced config \fBMarker Name\fP to the name of some file or folder that
you know will always exist in the folder.
.SS I really hate the \fB\&.stfolder\fP directory, can I remove it?
.sp
See the previous question.
.SS Am I able to use nested Syncthing folders?
.sp
Do not nest shared folders. This behaviour is in no way supported,