Files
restic/cmd/restic
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
..
2017-07-23 14:19:13 +02:00
2024-02-19 11:12:15 +01:00
2023-12-06 13:11:55 +01:00
2020-08-30 16:00:48 +02:00
2023-07-28 19:21:40 +02:00
2024-01-27 13:17:33 +01:00
2021-01-30 20:02:37 +01:00
2023-12-06 13:11:55 +01:00
2017-07-23 14:19:13 +02:00
2023-06-08 19:12:49 +02:00
2024-02-04 20:21:42 +01:00
2024-02-10 22:58:10 +01:00