[dtrace-discuss] Dtrace "fork()-o-meter" ...

[Adam Leventhal]

On Sat, Jan 13, 2007 at 10:51:15PM +0100, Roland Mainz wrote:
> > syscall::*fork*:entry
> 
> Note that just catching |fork()| is not enougth since some shells may
> use newer ways to spawn children (like |posix_spawn()| (if available and
> correctly working)).

Care to guess how posix_spawn is implemented? That said, proc:::create might
be a more stable choice.

> Grumpf... ten curses into the direction of the person who designed
> "dtrace"'s "-c" option like that... xx@@@!!!... ;-(

I thought that designing the rest of DTrace might have let us off the hook...

> Usual workaround (for shells) is to provide an EOF (or better:
> end-of-arguments) marker (and treat all arguments after this marker as
> "normal" ones again). This solution could be used for both the argument
> list after "-c" and the arguments passed to the Dtrace script. But I
> guess we can't fix that anymore and now have to live with this
> xx@@@!!!... ;-(

On the plus side, at least we don't have to suffer that EOF xx@@@!!!

- ahl

-- 
Adam Leventhal, Solaris Kernel Development       http://blogs.sun.com/ahl