Ctrl-C does not cleanly unmount

[s3ql]

Ctrl-C does not cleanly unmount

[Nikratio]

Thanks for the report! It is not clear to me that this is a bug rather than intended behavior. If Ctrl-C is indistinguishable from unmounting the file system (as it was in 2.31 and earlier), you could always just unmount the filesystem rather than pressing Ctrl-C. In 2.32 and newer, Ctrl-C results in the filesystem terminating as quickly as possible without data-loss (assuming that the local cache is kept).

Do you have a use case where you depend on Ctrl-C having the same semantics as unmounting?

[Salokyn]

Hi,
This is because I try to run s3ql in a docker container. So it must run in forground and must be unmounted cleanly when the container is stopped (when it is stopped, docker send a SIGTERM signal to the process running in the container).
When mount.s3ql --fg receives a SIGTERM or SIGHUP, it should cleanly unmount (whatever the time needed) and exit. This works fine in version 2.21 but crashes with v2.32.
Here is my project : https://gitlab.com/Salokyn/docker-s3ql

[Nikratio]

Thanks for the additional details! However, it is still not clear to me why you can't trigger a regular unmount before stopping the container, or as part of the container stopping procedure. Having a way to shutdown S3QL as quickly as possible without loosing data is a valuable feature, so I'm really not found of the idea of dropping this in favor of making SIGTERM/SIGHUP an alias for unmount.

[Nikratio]

I'm closing this bug report for now. Please feel free to re-open this if you can provide the requested information!