From: "ko1 (Koichi Sasada)" <redmine@...> Date: 2013-02-17T13:53:24+09:00 Subject: [ruby-core:52319] [ruby-trunk - Bug #5556] SIGHUP no longer ignored when sent to process group from a subprocess Issue #5556 has been updated by ko1 (Koichi Sasada). Assignee set to mame (Yusuke Endoh) ---------------------------------------- Bug #5556: SIGHUP no longer ignored when sent to process group from a subprocess https://bugs.ruby-lang.org/issues/5556#change-36362 Author: brixen (Brian Ford) Status: Feedback Priority: Normal Assignee: mame (Yusuke Endoh) Category: core Target version: 2.0.0 ruby -v: - Hi, Prior to 2.0.0dev, this script: sasha:rubinius brian$ cat process.rb puts "before system" system("ruby -e 'Process.kill(:HUP, 0)'") puts "after system" would print the following: sasha:rubinius brian$ ruby1.9.2 -v process.rb ruby 1.9.2p290 (2011-07-09 revision 32553) [x86_64-darwin10.8.0] before system after system Basically, SIGHUP was ignored when sent from a subprocess. Presently, this is the result: sasha:rubinius brian$ ruby -v process.rb ruby 2.0.0dev (2011-11-01 trunk 33596) [x86_64-darwin10.8.0] before system Hangup The following issue may be related, but the explanation is in Japanese, so I cannot follow it: http://redmine.ruby-lang.org/issues/4765 Is this change intentional? I discovered it running RubySpec, where there are specs for the behavior of sending SIGHUP to the process group. Thanks, Brian -- http://bugs.ruby-lang.org/