> If you are using ssh with unison, are you using the "KeepAlive yes" > option in your ssh configuration? If not, add it, and your connection > should not close from inactivity. If you are using direct sockets, > unison will use a keepalive so it can timeout if the communication link > is broken.
Well i was using it, but i found out the option was commented out on my host's config... i set it to yes and trying again now... will have results in a few mins.... > How long is unison taking to check for changes? I can usually reconcile > changes in my home directory (approximately 45G, 125,000 files) in less > than 10-15 seconds between my slow laptop drive and a remote machine. > However, if you are syncing with a Windows machine, expect the sync to > be much slower. Fast checking is not safe on Windows, as unison can miss > changes, so it scans every file every time unless you tell it otherwise. Well, the problem seems to be with my /usr/portage that had not been sync'ed for a long time (i guess it has to make thorough difference checking?). So there is lots of files to check. It really takes minutes to scan for changes, i'm timing this run, if it fails i'll post how long it takes to do the whole scan until it starts transfering and finds out it got timed out. Sync'ing is done from linux to linux. The problem is really hardware related; i'm thinking on getting a new portable HD, but since i'm about to loose my job,i might want to wait! ;) Thanks!
