3 ms·
This seems to rely on inotify which is not always triggered when files change when they are watched. In the following scenario realtime syncing would then fail
by qwertox 5y ago
This seems to rely on inotify which is not always triggered when files change when they are watched.
In the following scenario realtime syncing would then fail silently:
- You have a server A which contains files which you are editing.
- You have setup realtime syncing between server A and a machine B.
- On server A you have a Docker container which runs Samba and is hosting the directories of server A which contains the files you are editing.
- You are editing those files on a machine where you mounted those shares. Upon saving, the files on server A would be modified, but inotify would not trigger and the file would not get synced to machine B.
- zufallsheld 5y agoDid this happen to you? This seems like a very contrived example of a problem.
- qwertox 5y agoIt didn't happen with Syncthing because I'm not using it (yet!), but while trying to edit files normally which were watched by inotify. I'm kind of assuming that it's the containerization of Samba which is causing the problem, since I have not installed Samba directly on the server, but it could also be the case when not using Docker. Apparently any CIFS mount is affected https://lists.samba.org/archive/linux-cifs-client/2009-April/004319.html https://lists.samba.org/archive/linux-cifs-client/2009-April...
- Tor3 5y agoSyncthing has two methods for detecting file changes: Watching (inotify), and Scanning. Both are enabled by default, with scanning once per hour (+/- a random element). Configurable per directory. https://docs.syncthing.net/users/syncing.html https://docs.syncthing.net/users/syncing.html
- qwertox 5y agoExcellent, that's good to know.