Robert Alatalo
2009-Mar-31 14:21 UTC
[dtrace-discuss] Dtrace failing to find proc:::exit when run within zone
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:RAlatalo at Sun.com ~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~ 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.
bob netherton
2009-Mar-31 14:58 UTC
[dtrace-discuss] Dtrace failing to find proc:::exit when run within zone
Robert Alatalo wrote:> limitpriv: default,dtrace_proc,dtrace_user >These privileges only allow user level tracing (pid, fasttrap, profile and syscall). The vast majority of the probes you are seeing in the global zone is from fbt (kernel) and those are not allowed from inside a non-global zone. You really don''t want a non-global zone user to be poking around the kernel, do you ? See http://docs.sun.com/app/docs/doc/819-2450/gcogk?a=view for more info. Bob