-
-
Notifications
You must be signed in to change notification settings - Fork 401
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
Consider removing Signum.SIGHUP from the signals to terminate list #220
Comments
Why have you closed this? |
Because I realized that SIGHUP is responsible for proper notification and shutdown when the kill {pid} is used. So my solution won't really be a proper fix and instead it will just cause more issues for other users. |
Please excuse my lack of knowledge of Linux systems, but wouldn't removing |
It depends on how you attempt to kill it. By default, if you are using the kill {pid} command, the SIGTERM signal is sent.
|
If this is a bug report please make sure you have filled the following in:
(If it's not a bug and a feature request then just remove the below)
Plex Requests.Net Version:
Master branch.
Operating System:
FreeBSD-FreeNAS 9.10 STABLE
Mono Version:
4.2.2
Reproduction Steps:
Start the PlexRequests.exe on FreeBSD using
notice how the application shuts down as soon as it starts. This is important because of the way FreeBSD's init scripts work and how they cannot allow foreground blocking services.
Removing
from
fixes the issue. I think.
The text was updated successfully, but these errors were encountered: