Hi Adam, I continue being interested in solving the problem - just was out of office yesterday.
I get this strange behavior when (as non-root with dtrace-proc and dtrace-user privs) I try to trace a process in a non-global zone (running there under my account, same privs) from the global zone. This already is my "fallback" path, because my first attempt (to do the tracing in the non-global zone where the process is running) failed with "dtrace: failed to initialize dtrace: DTrace device not available in local zone" I get the same effect with a variant of the classic "hello, world"-program when trying to trace it in the same manner (cross-zone, as described above). But everything works as expected when I'm running both the "hello, world"-program and dtrace in the global zone. Unfortunately running the server-process in the global-zone isn't a practicable path, because this process depends heavy on the versions of installed third-party libraries, which differ between the zones. Thomas -- This message posted from opensolaris.org _______________________________________________ dtrace-discuss mailing list [email protected]
