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 <stanislav.kholmansk...@oracle.com> > > Could anybody look at this patch, please?
Looks OK to me, acked. -- Cyril Hrubis chru...@suse.cz ------------------------------------------------------------------------------ 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 Ltp-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ltp-list
