mirror of
https://github.com/restic/restic.git
synced 2024-09-30 14:21:16 +02:00
30e979d252
The previous code only ran cleanup (lock release for example) on SIGINT. For anyone running restic in a container, the signal is going to be SIGTERM which means containerized execution would leave locks behind. While this could be addressed via interposing dumb-init to translate the signal, a `kill` invocation is going to default to SIGTERM, so the same problem exists for non container users. Signed-off-by: Brian Harring <ferringb@gmail.com> |
||
---|---|---|
.. | ||
restic |