Why still using unison over cygwin?
2.40.16 supports Unicode, so no problem syncing between Win/Linux/Mac.
(The first two of them I can confirm)
If you want to give it a try, sync your directories (if not working with
2.40.16, then with an older version which worked for you) and after that
sync directly with 2.40.16 without cygwin (I use putty/plink for ssh).
“The debug message” is from Option -debug all? Or is this just what it
prints out if you start the commando without debug option?
Regards,
*Von:* unison-users@yahoogroups.com
[mailto:unison-users@yahoogroups.com] *Im Auftrag von *Robert Schmidt
*Gesendet:* Dienstag, 28. September 2010 15:03
*An:* unison-users@yahoogroups.com
*Betreff:* [unison-users] unison 2.40.16 (cygwin) over ssh doesn't
resume after merge command
Hi,
After the upgrade to 2.40.16, I've had problems with unison simply
freezing when the merge command has finished - as if it is still waiting
for the process to exit.
This always happens when syncing local to a remote location over ssh,
but never when syncing two local roots.
A sample command line (using a simple cp instead of my merge script):
unison -root / -root ssh://mylogin@myserver// <ssh://mylogin@myserver/>
-path
home/private/Documents/test.txt -merge "Name {*.txt} -> cp CURRENT1 NEW"
-backupcurrent "Name {*.txt}" -debug all
The last debug message is:
Merge command: cp '/home/private/Documents/.unison.merge1-test.txt'
'/home/private/Documents/.unison
.mergenew1-test.txt'
After which, unison seems to wait indefinitely.
Is this a known bug, or am I doing something wrong?