Re: [LTP] [PATCH] sigaction 9-1, 10-1, 11-1: use SIGKILL instead of SIGHUP

[Stanislav Kholmanskikh <stanislav.kholmanskikh@oracle.com>]

Hi!

On 04/25/2014 01:46 PM, Stanislav Kholmanskikh wrote:
> There are test environments, where the SIGHUP signal may be either
> added to the signal mask or ignored. One example of such environments
> is Autotest, which sets the SIGHUP signal to SIG_IGN for its jobs.
>
> Therefore the above test cases hang in that environment because their
> parent processes send SIGHUP to terminate the child (and the child ignores it).
>
> I think it will not be a problem to use SIGKILL here instead of SIGHUP, because
> SIGKILL can not be caught, blocked, or ignored.
> And it does the job - stopping the child - very well :)
>
> Signed-off-by: Stanislav Kholmanskikh <stanislav.kholmanskikh@oracle.com>

Could anybody look at this patch, please?

Thanks.

------------------------------------------------------------------------------
Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
&#149; 3 signs your SCM is hindering your productivity
&#149; Requirements for releasing software faster
&#149; Expert tips and advice for migrating your SCM now
http://p.sf.net/sfu/perforce
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list