Skip to content

Shotgun Doesn't Respond to SIGTERM #33

Closed
Wardrop opened this Issue Aug 17, 2011 · 3 comments

3 participants

@Wardrop
Wardrop commented Aug 17, 2011

Shotgun does not seem to respond to the SIGTERM process signal, which can make starting and stopping shotgun and real pain, as the common CTRL+C doesn't kill it. Is there any reason for this? If not, is it something that can be fixed in a future version?

Cheers

@Wardrop
Wardrop commented Aug 17, 2011

I've found that indeed it does quit with CTRL+C, but only if it's served a HTTP request. If you start shotgun and hit CTRL+C before issuing a HTTP request, it will not terminate until it receives the first request. So still something that should be fixed. I'm running Ubuntu 11.04 by the way.

@pyrat
pyrat commented Aug 17, 2011

I am experienced a similar issue with WEBrick and CTRL + C not working.


^C[2011-08-17 10:26:27] ERROR Interrupt:
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/webrick/server.rb:91:in `select'

I'll try with different ruby versions and report back.

@djanowski
Collaborator

It's working for me, even on 1.8.7. So please reopen if still an issue.

@djanowski djanowski closed this Mar 1, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.