SIGTERM handling

[arietto]

Hello! Why is void UnixFork::handleSigTerm() body inactive?
I have to use QProcess, which starts and stops cutelyst-wsgi2. QProcess emits SIGTERM within terminate(). What would you advise?

[arietto]

Would you like to consider https://github.com/Skycoder42/QCtrlSignals for inspiration?

[arietto]

BTW,
/**
* This signal is likely to be emitted when the worker process should
* stop, at this point the application has a limited time to finish it's
* operations, if a timeout is reached the application will get killed.
*/
void shuttingDown(Application *app);
Where is this timeout hardcoded? I just have one master process without workers (I don't need concurrent workers).

[arietto]

Should I add SIGTERM to case in void UnixFork::setupSocketPair(bool closeSignalsFD, bool createPair)?

 case SIGINT:
 case SIGQUIT:
 handleSigInt();
 break;

[dantti]

hmm I don't recall why I don't handle SIGTERM, one thing I've looked into that project some time ago was to Fix CTRL+C on Windows, which ATM crash.

[arietto]

And what about void shuttingDown(Application *app); timeout? I have to emit signals in the corresponding slot slotShuttingDown in order to gracefully terminate some non-Cutelyst threads. Sometimes I receive a log message which shows that QThread was deleted but the thread is still active.

[dantti]

This might be fixed with commit 6e56383