Brian Harring 30e979d252

Catch SIGTERM, run cleanup ...

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>

2024-02-19 11:12:15 +01:00

..

restic

Catch SIGTERM, run cleanup

2024-02-19 11:12:15 +01:00