问题原文
原帖链接 · ardabro · CC BY-SA 3.0
I've just compiled unison 2.48.4 for my own. It works perfectly after normal call but unison-fsmonitor doesn't deect any filesystem changes and doesn't synchronize anything. Filesystem is EXT4.
-debug all/verbose doesn't bring any log. The only thing it puts on the terminal is VERSION 1, after hitting any key it terminates with message: ERROR unknown%20command%20''
No mater whether invoked with sudo or as regular user.
Nothing in ~/.unison/unison.log
Any ideas about the possible reasons? Any ideas how to debug it?
已采纳解答
原帖链接 · Mike Pierce · CC BY-SA 3.0
The executable unison-fsmonitor is not meant to be run on its own, but is instead just a tool that Unison uses to watch your filesystem. To have Unison watch your filesystem for changes just run unison with the line repeat=watch in your profile, or from the command line run
unison -repeat watch
摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。
