Libraries?
I copy the unison.exe to the target and host systems (in the path), then invoke
Unison path UNC_path
and it works... Uses NetBIOS copy in this mode.
If I want to do multiple syncs or higher performance, I install unison on my server as a service with SrvAny, listening on a socket (unison -socket:1234). Then I run Unison on the client as
Unison socket:server:port/D:\path d:\path
You can even launch the socket listener manually to do a quick test!
Simple, really. All that library crap is if you want to run as a GUI in Windows, which requires manual interaction. The C/L version is very powerful, needs no installation or files other than the executable. If you get fancy, you should define a UNISON environment var to point to a default folder where the logs, profiles, and archive records are kept.
Glenn
_________________________
Actually I
am a Rocket Scientist!
