reassign 366391 openssh-client severity 366391 normal unarchive 313371 forcemerge 313371 366391 quit
Hi Mario, Mario Iseli wrote: > is there already a fix available? In an ideal world, maybe svn wouldn't have to kill the ssh process. That might even be possible, but that's another story. See [1] for more on this. Friendly programs accept SIGTERM by just shutting down without complaining, but some versions of the ssh client were not so graceful, and svn sent SIGKILL instead for a while to work around that. There were some bad consequences, and once the ssh client was fixed, svn switched to SIGTERM[2]. This bug report was about the resulting message "Killed by signal 15". It was fixed in the openssh-client package. Thanks for reporting, Jonathan [1] http://subversion.tigris.org/issues/show_bug.cgi?id=2580 [2] http://bugs.debian.org/335528 -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
