On 05/05/2014 03:10 PM, [email protected] wrote: > Hi!
Hi! >>> 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 <[email protected]> >> >> Could anybody look at this patch, please? > > Looks OK to me, acked. > Thank you. Pushed. ------------------------------------------------------------------------------ Is your legacy SCM system holding you back? Join Perforce May 7 to find out: • 3 signs your SCM is hindering your productivity • Requirements for releasing software faster • Expert tips and advice for migrating your SCM now http://p.sf.net/sfu/perforce _______________________________________________ Ltp-list mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ltp-list
