mirror of
https://github.com/octoleo/lsyncd.git
synced 2024-06-01 07:50:51 +00:00
.
This commit is contained in:
parent
930105744d
commit
1975f2a22f
|
@ -4,3 +4,4 @@ title: Frequently Asked Questions
|
||||||
short: FAQ
|
short: FAQ
|
||||||
---
|
---
|
||||||
* [How can I call a script after each rsync operation?](postscript)
|
* [How can I call a script after each rsync operation?](postscript)
|
||||||
|
* [The startup sync works but after that Lsyncd doesn't do anything](nothing-after-startup)
|
||||||
|
|
11
faq/nothing-after-startup/index.md
Normal file
11
faq/nothing-after-startup/index.md
Normal file
|
@ -0,0 +1,11 @@
|
||||||
|
---
|
||||||
|
layout: default
|
||||||
|
title: "FAQ: The startup sync works but after that Lsyncd doesn't do anything"
|
||||||
|
---
|
||||||
|
This almost always caused by the fact you specified a network mounted directory as source.
|
||||||
|
|
||||||
|
Lsyncd requires the kernels inotify or fsevents interface to get noted of file changes. No known network filesystem (known to Lsyncd authors) supports forwarding file notifcations events.
|
||||||
|
|
||||||
|
Thus Lsyncd needs to run on the system where the files are located physically.
|
||||||
|
|
||||||
|
## [‹‹ back to FAQ index](../)
|
Loading…
Reference in New Issue
Block a user