[Bug uprobes/6841] system-wide utrace syscall tracing script don't respond signal

["dsmith at redhat dot com" <sourceware-bugzilla at sourceware dot org>]

------- Additional Comments From dsmith at redhat dot com  2008-08-14 21:08 -------
Here's a somewhat unrelated issue.  Here's the output of the original script
after 5 seconds on a system not really doing anything:

  audispd(1526) issues syscall 2 times
  rsyslogd(1547) issues syscall 11 times
  hald-addon-stor(1794) issues syscall 7 times
  automount(1814) issues syscall 20 times
  setroubleshootd(1832) issues syscall 6 times
  sendmail(1969) issues syscall 10 times
  kerneloops(2005) issues syscall 5 times
  stapio(4070) issues syscall 53 times

Here's the same output with the timer set to 30 seconds:

  auditd(1524) issues syscall 2 times
  audispd(1526) issues syscall 3 times
  rsyslogd(1547) issues syscall 11 times
  rpcbind(1565) issues syscall 3 times
  hald(1698) issues syscall 4 times
  hald-addon-stor(1794) issues syscall 13 times
  automount(1814) issues syscall 120 times
  setroubleshootd(1832) issues syscall 31 times
  ntpd(1949) issues syscall 40 times
  sendmail(1969) issues syscall 55 times
  crond(1996) issues syscall 28 times
  kerneloops(2005) issues syscall 13 times
  stapio(4288) issues syscall 303 times

Over 5 and 30 seconds, stapio was the biggest issuer of system calls by far. 
stapio may be polling too often.

-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=6841

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.