Hello,
martin f krafft writes:
also sprach [EMAIL PROTECTED] <[EMAIL PROTECTED]> [2007.04.04.1311 +0200]:
I understand perfectly your position... i don't say that your request is
not good, but the current behavior is "a sane default". I think unison
developper won't pay attention to things that require to change a lot of
things making the whole thing very complicated... Recovering from
unexpected interrupt is a tricky business, i hope you understand that
unison team try to keep the thing simple (i talk as maintainer of unison
since i am not part of unison team -- maybe they will agree without
discussion to your request).
Yes, I understand, and I do not have a good solution to propose.
Maybe the limitation could be documented in the manpage though?
Synchronisation and file transfers cannot be resumed if they're
cancelled in the middle of transfer entities, which could be files,
or directories if the entire directory is new.
I think your request can be partially solve this way:
* propose a solution for bug 417620 (limit the number of simultaneous file
transfer)
* write in README.Debian that sync cannot be resumed and that for slow link
it is better to use less simultaneous file transfer
What do you think about ?
Regards
Sylvain Le Gall
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
