I’ve merged PR #1564 today which changes the way the ssh
program is run for the sftp
backend. The problem was that when users press CTRL+C, the terminal sends a SIGINT
signal to both the restic process and the ssh
process, causing the ssh
process to exit immediately. restic was then unable to remove the lock file and an error was returned.
The first try to mitigate that was starting the ssh
process in its own “Process Group”, but then ssh
is unable to use the TTY and ask the user for a password.
With the new code, ssh
is still run in its own process group, but this time it is set to be the “foreground process group” until the sftp
connection is established.
So, it’d be awesome if some of you could test the new code with the sftp backend and report back if:
- SSH correctly queries for a password (if necessary)
- Cancelling e.g. a
check
operation correctly removes the lock file from the repo
You can find a precompiled binary of today’s master branch here: https://beta.restic.net/restic-v0.8.1-55-g663e8284/
Thanks!