ok,
Thanks for the info - I guess this sort of is asking for it, but exactly how
did you know that 5 was the right number to grep for, aside from knowing the
kernel?
Also, isn't stop, being a destructive actions, not allowed without
dtrace_kernel privilege? Shouldn't I - as a user, be able to add destructive
actions that modify my own processes, and nobody else's?
To the first point, IMO, there should be an 'intelligent' copyinstr - one that
is able to either dereference if needed, and one that converts common numbers
like the above into human-readable actions. I'd love to be able to say:
dtrace -n 'syscall:::entry { @[ execname, pid, probefunc, copyinstr(arg0, arg1,
arg2) ] = count(); }'
and not have to worry whether a given function had 3 arguments or 2 or 1 --
that it would do the right thing and basically give me human readable output
for all system calls on the system without need for lots of programming. (the
other place this would be helpful for is door calls. I'm still not sure how to
trace past these.)
As for the second point, IMO there has got to be a level between dtrace_user
and dtrace_kernel, perhaps 2 - one where you can effect (ie: have destructive
actions) on your own processes, and one where you can effect and/or trace
processes in your own groups - often, the functions I need to trace past are
ones done by, say a web server, and I don't want to need sudo or root privilege
to do this. Just MO.
Thanks again,
Paul
(PS: can you write user-based dtrace functions? that would be a quick fix for
the intelligent copyinstr feature.. and would come in helpful in a myriad of
ways..)
--
This message posted from opensolaris.org
_______________________________________________
dtrace-discuss mailing list
[email protected]
