On Nov 26, 2007, at 11:09 AM, Bryan Cantrill wrote:
>
> Zone ID may not be a good example of what you're talking about -- for
> pr_zoneid, I think you should act as a Solaris machine would if it had
> no installed zones. (That is, always return 0 for pr_zoneid to
> denote the
> global zone.) There may be more convincing examples where there is no
> mapping in the OS X world, but I find it hard to accept that you
> shouldn't
> just refuse to translate such members and let the compile fail.
Yes, I just remembered a much better example:
curpsinfo->pr_psargs
The data needed to properly populate this field does not exist in
OS X. Should DTTk's newproc.d fail to compile, or should it produce
the marginally useful:
ghopper:/# newproc.d
dtrace: script '/usr/bin/newproc.d' matched 2 probes
CPU ID FUNCTION:NAME
0 18481 __mac_execve:exec-success sh
0 18481 __mac_execve:exec-success hostname
0 18481 __mac_execve:exec-success bash
0 18481 __mac_execve:exec-success id
1 18481 __mac_execve:exec-success login
1 18481 __mac_execve:exec-success cat
3 18481 __mac_execve:exec-success tcsh
I'm certain there are other equally annoying areas of impedance
mismatch, its just been a long time since I had this discussion and
don't
remember them all.
James M
_______________________________________________
dtrace-discuss mailing list
[email protected]
