Garrett Cooper said the following on 2011-6-30 9:21: > This seems like it would produce undesirable results when what you > want to do is actually make sure that the syslog tests bring rsyslogd > back to life after the test is done; all tests should setup any > necessary environment to run the test, and restore the original state > of the system if at all possible -- otherwise it becomes a mess > getting everything to integrate properly. Restarting rsyslogd after > the syslog tests are done isn't that hard, so that should be done > there.
The syslog tests restart rsyslogd to restore the original state, but ltp-pan will kill rsyslogd when it kills orphans. rsyslogd can use setsid() or ioctl() to make itself a daemon. In RHEL, rsyslogd uses ioctl(). But TIOCNOTTY ioctl cannot remove it from its current process group, so ltp-pan will still kill it. -- Best Regards, Peng Haitao ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ Ltp-list mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ltp-list
