Re: Accessing probe info synchronously

[Lasse Bigum <zenith at cs dot aau dot dk>]

On 10:18, Fri 09 Feb, Frank Ch. Eigler wrote:
> Lasse Bigum <zenith@zenith.dk> writes:
> > As to how we notify the IDS of the system call, the application that
> > tried to do it, and what parameters was used for the system call,
> > well that is what is missing from our puzzle now I think :) [...]
> 
> It sounds like this part can travel along the usual output stream
> via ordinary printf's.

We have settled on using sockets for the communication I think, so would
you suggest doing what I saw done in one of the war stories then:
"stap -x <pid> some-stap-script.stp | <some-socket-to-ids-program>
-socketname"
?

As there seem to be no other way to get info out of a stap script than
parsing stdout, this seems to be the way forward or what?

From what I can tell, it seems that sockets can be made non-blocking, so
would using them directly from a stap-script be possible?

Thanks in advance

/Lasse

Attachment: smime.p7s
Description: S/MIME cryptographic signature