100% cpu use after killing bn ssh; doesn't log or email error
Hi!
Backupninja was running an automated rdiff-backup script. I noticed with nethogs that the ssh connection was slow (not backupninja's fault), so I decided to kill the ssh process.
the rdiff-backup thread quit but backupninja started using 100% cpu. It had two process forks and one of them was 100% active, and the others not so much. After about a half hour, backupninja continued on its merry way to the next backup config. I'm not sure what it was doing there.
Once backupninja was done I did not receive any email or see any log message reporting an error. I'm concerned about what might happen if a ssh connection dies unexpectedly.
Thanks for your wonderful program!
(from redmine: created on 2015-08-27, closed on 2015-08-31)