On Mon, Nov 19, 2012 at 09:35:26AM -0500, Dave Abrahams wrote: > One thing I notice sometimes is that after I've suspended and woken my > computer an mbsync job will get "stuck," neither exiting or seeming to > make any forward progress. Is there a cure for this other than > monitoring and explicitly killing the job? > mbsync has no timeout handling whatsoever. if you suspend the machine while it should receive data, the packets will be simply lost and it will wait for them forever until the connection is reset for some reason. patches welcome ... you "only" need to implemement some simple timer support in the mainloop, and hook that up with connection objects. ^^
------------------------------------------------------------------------------ Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov _______________________________________________ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
