Skip to content
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

"The SIGHUP signal is sent to a process when its controlling terminal is closed" #4

Open
s6577t opened this issue Jul 15, 2013 · 3 comments

Comments

@s6577t
Copy link
Contributor

s6577t commented Jul 15, 2013

https://en.wikipedia.org/wiki/Unix_signal

If you run socketmaster -command my_command & and then close the shell, socket master will start a new child process

Maybe use USR2 instead?

@s6577t
Copy link
Contributor Author

s6577t commented Jul 25, 2013

nope. HUP is also used by unicorn. I started a Go process started via an ssh session, put it into the bg and then closed the ssh session, no HUP signal was received.

@s6577t s6577t closed this as completed Jul 25, 2013
@zimbatm
Copy link
Owner

zimbatm commented Jul 25, 2013

OK thanks for confirming this. I had seen HUP being used for soft reloads
in the past so it seemed appropriate.
On Jul 25, 2013 10:03 AM, "Sam Taylor" [email protected] wrote:

nope. HUP is also used by unicorn. I started a Go process started via an
ssh session, put it into the bg and then closed the ssh session, no HUP
signal was received.


Reply to this email directly or view it on GitHubhttps://github.com/pandastream/socketmaster/issues/4#issuecomment-21541378
.

@s6577t
Copy link
Contributor Author

s6577t commented Jul 25, 2013

yeah. I tried it out on Darwin and Debian (ubuntu).

@s6577t s6577t reopened this Jul 25, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants