* Maxim Veksler <[EMAIL PROTECTED]> [070320 19:14]:
> On 3/20/07, Baruch Even <[EMAIL PROTECTED]> wrote:
> >* Maxim Veksler <[EMAIL PROTECTED]> [070320 15:57]:
> >> btw, too bad http://syscalltrack.sourceforge.net/ ain't good(?) for 2.6.
> >
> >You can get a similar effect by using systemtap on a kprobes enabled
> >kernel. It's actually much stronger than syscalltrack.
> >
>
> Thanks for the tip. It's an interesting utility, but not suitable for
> production (IMHO).
> I need to monitor a very low and minor activity on a production
> server, doing a kernel level break point for traps just sounds bad.
I was using kprobes for a high rate test and it worked wonderfully.
There was no systemtap at the time so I had C code in the kernel to
handle the kprobe but systemtap simply generates a module and loads it
into the kernel AFAUI.
For a low level activity it will be fine. I had to go with a different
approach at the end because my work was about timing the execution and
the breakpoints messed up my timing, but if you need functionality
rather than timing information it should be a great option.
systemtap is written as an equivalent to DTrace of Solaris and is meant
to be used on production machines, the mailing list is helpful as well
but I found their examples fairly simple to understand and adapt when I
tried it again lately.
> How do I check if my kernel was compiled with kprobes?
Either you have /proc/config{,.gz} support or you have
/boot/config-<kver> file and look for KPROBE.
Baruch
=================================================================
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]
