Rick Fiorentino wrote: > Hi Jeremy, > Doesn't appear to work even in debug mode on Windows. Let me know if you > need additional info or if I goofed up the testing.
You didn't goof anything up, it's setting up the signals in scgi that is the problem. Try this patch to ruby-scgi: diff --git a/lib/scgi.rb b/lib/scgi.rb index 8852da2..44200ce 100755 --- a/lib/scgi.rb +++ b/lib/scgi.rb @@ -254,8 +254,13 @@ module SCGI def setup_signals trap("TERM") { @log.info("SIGTERM, forced shutdown."); shutdown(force=true) } trap("INT") { @log.info("SIGINT, graceful shutdown started."); shutdown } - trap("HUP") { @log.info("SIGHUP, graceful shutdown started."); shutdown } - trap("USR2") { @log.info(status_info) } + begin + trap("HUP") { @log.info("SIGHUP, graceful shutdown started."); shutdown } + trap("USR2") { @log.info(status_info) } + rescue ArgumentError + # Probably on Windows and these signals aren't supported + nil + end end # Returns a Hash with status information. This is used If this helps, I'll put out a 0.9.1 ruby-scgi release. Jeremy -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---