Over an hour ago, my cron agent (fcron) started syncronizing my email. Shortly after it began, I suspect the following happened: I disconnected from that network and connected to a different one, using a different interface. mbsync still thought the old connection was valid and hung around, since I never actually let the connection to the server terminate gracefully.
That mbsync process is still running. Would it be possible to have a CLI flag or compiled default number of seconds after which mbsync gives up and decides that it won't be getting any more network traffic after all? Alternate suggestions for what could be wrong, how it could be fixed, discussion on if it should be fixed, or suggestions that I should write the above functionality before complaining, are all welcome. Thank you for your time, - Toyam ------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e _______________________________________________ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
