On Mon, Jul 11, 2011 at 8:31 PM, Wanlong Gao <[email protected]> wrote: > According to the Linux kernel code, we know that the sigqueue is > allocated and queue the signal to it's list by the system call > rt_sigqueueinfo(2) which called by sigqueue(3) in this test code. > Meanwhile, if the signal is queued, it increase the user's sigpending > field. Then if it going to queue another signal, it read the rlimit of > the sigpending from the task's signal->rlim[] member and compare with > the user's current sigpending number. > So, it's the issue. The user who is running this code may have other > pending signals before this, and actually it does. > > This patch read the pending signal's number from the /proc/<pid>/status > and minus it. Eliminate the impact of other pending signals.
Not portable outside of linux. Thanks, -Garrett ------------------------------------------------------------------------------ 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
