On 18 October 2011 10:34, Karl Berry <[email protected]> wrote: > Also, I remind you that there's evidently another (or the same) > problem on Savannah that drops the connection after 1 hour. > > Due to runaway processes killing the system, we instituted that > hardwired timeout some time ago: > > exec timeout 60m /usr/bin/bzr "$@" > > I just increased it to 120m. > > I know of no feasible way to determine whether the connection is > actually active. I can imagine various infeasible ways, but I think > they would all cause more trouble than they would save. I hope it is > merely a matter of rerunning the command that got killed off at the > magic moment, so not losing significant amounts of work.
bzr 2.5b2 has a builtin timeout to drop idle connections <http://pad.lv/824797>. I don't know if that would fix the "go crazy" case. If you see that, please file a bug with a traceback and/or strace. m
