public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* Tracing each new process...
@ 2002-08-01 11:46 Fabrizio Morbini
  2002-08-01 17:04 ` Karim Yaghmour
  0 siblings, 1 reply; 4+ messages in thread
From: Fabrizio Morbini @ 2002-08-01 11:46 UTC (permalink / raw)
  To: Linux Kernel Mailing List

Hi, somebody know how signaling the creation of each new process?
(watching the proc filesystem or ps output is too slow)

If this software doesn't exists where (in the kernel source) I must
insert hook for tracing the creation of new process?

Thank you very much for any help!!

Fabrizio.


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Tracing each new process...
  2002-08-01 11:46 Tracing each new process Fabrizio Morbini
@ 2002-08-01 17:04 ` Karim Yaghmour
  2002-08-01 17:13   ` Muli Ben-Yehuda
  0 siblings, 1 reply; 4+ messages in thread
From: Karim Yaghmour @ 2002-08-01 17:04 UTC (permalink / raw)
  To: Fabrizio Morbini; +Cc: Linux Kernel Mailing List


Have a look at the Linux Trace Toolkit:
http://www.opersys.com/LTT/

Fabrizio Morbini wrote:
> Hi, somebody know how signaling the creation of each new process?
> (watching the proc filesystem or ps output is too slow)
> 
> If this software doesn't exists where (in the kernel source) I must
> insert hook for tracing the creation of new process?
> 
> Thank you very much for any help!!
> 
> Fabrizio.
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

-- 
===================================================
                 Karim Yaghmour
               karim@opersys.com
      Embedded and Real-Time Linux Expert
===================================================

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Tracing each new process...
  2002-08-01 17:04 ` Karim Yaghmour
@ 2002-08-01 17:13   ` Muli Ben-Yehuda
  2002-08-01 17:25     ` Karim Yaghmour
  0 siblings, 1 reply; 4+ messages in thread
From: Muli Ben-Yehuda @ 2002-08-01 17:13 UTC (permalink / raw)
  To: Karim Yaghmour; +Cc: Fabrizio Morbini, Linux Kernel Mailing List

[-- Attachment #1: Type: text/plain, Size: 687 bytes --]

On Thu, Aug 01, 2002 at 01:04:51PM -0400, Karim Yaghmour wrote:
> 
> Have a look at the Linux Trace Toolkit:
> http://www.opersys.com/LTT/

syscalltrack, http://syscalltrack.sourceforge.net can do it as
well. You'll get the notification in user space out of the box, and in
kernel space with a bit of hacking. 

> Fabrizio Morbini wrote:
> > Hi, somebody know how signaling the creation of each new process?
> > (watching the proc filesystem or ps output is too slow)
> > 
> > If this software doesn't exists where (in the kernel source) I must
> > insert hook for tracing the creation of new process?
-- 
http://vipe.technion.ac.il/~mulix/
http://syscalltrack.sf.net/

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Tracing each new process...
  2002-08-01 17:13   ` Muli Ben-Yehuda
@ 2002-08-01 17:25     ` Karim Yaghmour
  0 siblings, 0 replies; 4+ messages in thread
From: Karim Yaghmour @ 2002-08-01 17:25 UTC (permalink / raw)
  To: Muli Ben-Yehuda; +Cc: Fabrizio Morbini, Linux Kernel Mailing List


Muli Ben-Yehuda wrote:
> On Thu, Aug 01, 2002 at 01:04:51PM -0400, Karim Yaghmour wrote:
> >
> > Have a look at the Linux Trace Toolkit:
> > http://www.opersys.com/LTT/
> 
> syscalltrack, http://syscalltrack.sourceforge.net can do it as
> well. You'll get the notification in user space out of the box, and in
> kernel space with a bit of hacking.

Syscalltrack is only for tracking system calls. If the process creation
was requested from user-space, then indeed syscalltrack will show it.
It won't see kernel threads, among many other things. Not to mention
that it has to play around with the system call table to get its
information.

Now that you mention it, however, it is clear to me that syscalltrack
could definitely use the tracing framework provided by LTT in many
areas. First and foremost, it could get its system call information
using the existing trace hooks provided by LTT. In addition, instead
of implementing yet another event buffering framework, it could
use LTT's trace driver which already provides very efficient buffering.

Yet another reason to include LTT in the kernel.

Karim

===================================================
                 Karim Yaghmour
               karim@opersys.com
      Embedded and Real-Time Linux Expert
===================================================

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2002-08-01 17:31 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-08-01 11:46 Tracing each new process Fabrizio Morbini
2002-08-01 17:04 ` Karim Yaghmour
2002-08-01 17:13   ` Muli Ben-Yehuda
2002-08-01 17:25     ` Karim Yaghmour

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox