I don't know a lot about unix signal handling, but don't unix signals need to be handled synchronously? Or can we watch for SIGTERM, call nsIAppStartup.quit(), and return from the signal handler immediately, allowing the eventloop and stack to unwind gracefully later?
Should SIGTERM cause eAttemptQuit (prompting the user if there is unsaved work/multiple tabs), or eForceQuit?
I don't know a lot about unix signal handling, but don't unix signals need to be handled synchronously? Or can we watch for SIGTERM, call nsIAppStartup. quit(), and return from the signal handler immediately, allowing the eventloop and stack to unwind gracefully later?
Should SIGTERM cause eAttemptQuit (prompting the user if there is unsaved work/multiple tabs), or eForceQuit?