Hello,
A simple script runs fine within the global zone but fails when run in
a local zone. Running dtrace -l both in the local zone and global zone lists
problems but the local zone has far fewer probes and not name exit.
$ wc -l local-zone-dtrace-l.txt global-zone-acttxtest1.dtrace-l.log
495 local-zone-dtrace-l.txt
71953 global-zone-acttxtest1.dtrace-l.log
72448 total
So, less than 500 compared to more than 71 thousand in the global zone... so
anyone have suggestions?
The zone seems to have the following set:
limitpriv: default,dtrace_proc,dtrace_user
thank in advance for any suggestions,
Robert
--
If you would prefer to be contacted via phone or e-mail. Please
let me know.
=================================================================
=================================================================
Robert Alatalo ~ Technical Support Engineer
Sun Microsystems, Burlington, MA 01803
Phone:781-442-1301, Fax:781-442-1655 , E-mail:[email protected]
~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~
ONLINE SUPPORT CENTER: http://www.sun.com/service/online
~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~
All information in this e-mail is Sun Microsystems privileged,
confidential information and intended for addressee(s) only.
_______________________________________________
dtrace-discuss mailing list
[email protected]
