-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SIGTERM is not handled properly #35
Comments
It probably is related to signal(7) and multi-threading (see pthreads(7), nptl(7) and clone(2) ...), a topic known to be delicate. An explanation or workaround could be inspired by Qt5 and Unix signals; see also of course signal-safety(7) and sigevent(7) .... |
Asked https://stackoverflow.com/q/61370635/841108 still buggy in commit b616def |
Still buggy in commit 2ae9549 using https://stackoverflow.com/a/61374592/841108 |
Perhaps we need to use pipes. See https://doc.qt.io/qt-5/unix-signals.html for an explanation or inspiration and pipe(7) and signal-safety(7). |
Partly fixed in commit 400aa4a |
In commit cb8aabd we still have this reproducible issue. It seems related to httplib.
I am very tempted to give up using httplib.h; for our case, it seems unreliable. |
This problem happens because you don't call
|
In commit f5a5e81 the
SIGTERM
signal is not handled as it should be by signalfd(2) facilities of C++ filehcv_background.cc
To exercise the bug after suitable configuration, run
then (in some other terminal)
kill $(cat /tmp/helpcovid.pid)
The text was updated successfully, but these errors were encountered: