diff options
Diffstat (limited to 'bugs/obnam_should_handle_user_abort___40__ctrl-c__41___and_SIGTERM_gracefully.mdwn')
| -rw-r--r-- | bugs/obnam_should_handle_user_abort___40__ctrl-c__41___and_SIGTERM_gracefully.mdwn | 23 |
1 files changed, 0 insertions, 23 deletions
diff --git a/bugs/obnam_should_handle_user_abort___40__ctrl-c__41___and_SIGTERM_gracefully.mdwn b/bugs/obnam_should_handle_user_abort___40__ctrl-c__41___and_SIGTERM_gracefully.mdwn deleted file mode 100644 index 2c13c25..0000000 --- a/bugs/obnam_should_handle_user_abort___40__ctrl-c__41___and_SIGTERM_gracefully.mdwn +++ /dev/null @@ -1,23 +0,0 @@ -When I abort a backup using ctrl-c I get a stale lockfile on the sftp-Server - -Current (1.0) behavior: - - bart ~ # obnam backup --root=/etc - Enter passphrase for key '/home/mschiff/.ssh/id_dsa': - 00h00m03s 1286 files; 0 B (0 B/s) /etc/runit/runsvdir/all/getty-tty2 ^C Killed by signal 2. - (here I had hit ctrl-c) - bart ~ # obnam backup --root=/etc - Enter passphrase for key '/home/mschiff/.ssh/id_dsa': - ERROR: Lock timeout - bart ~ # - ---- - -Yeah. Obnam does not always clean up the lock files when it crashes. For some crashes it's not even possible. You can use the "obnam force-lock" command to remove the lock files, if you're sure they are not from another client using the same repository. --liw - -mschiff: You consider pressing ctrl-c to abort a backup a "crash" ? - -It's a user-induced crash, yes. It's one of the situations where Obnam could clean up, and it probably should. I believe there is a bug open about that already. --liw - - -[[done]] |