Sun Microsystems 10 User Manual
Version 3.1-en
Solaris 10 Container Guide - 3.1 4. Best Practices
Effective: 30/11/2009
4.5.6. DTrace of processes within a zone
[dd/ug] DTrace can be used to examine processes in zones. To do so, DTrace scripts can be
extended by the variable zonename in order to e.g. only trace system calls of a zone
[dd/ug] DTrace can be used to examine processes in zones. To do so, DTrace scripts can be
extended by the variable zonename in order to e.g. only trace system calls of a zone
global# dtrace -n 'syscall:::/zonename==”sparse”/
{@[probefunc]=count()}'
{@[probefunc]=count()}'
or to measure the I/O of zones.
global# dtrace -n io:::start'{@[zonename] = count()}'
Starting with Solaris 10 11/06, DTrace can also be applied to processes within the own local zone.
The privileges dtrace_proc and dtrace_user need to be assigned to the zone
(zonecfg:set limitpriv=default,dtrace_proc,dtrace_user). Kernel tracing,
and the tracing of processes in the global zone, remains excluded. DTrace within a zone is of interest
especially for those use cases where a zone is used for software development or where the
administration of a zone was delegated. In this case, the local zone administrator is able to analyze
independent of the platforms administrator.
The privileges dtrace_proc and dtrace_user need to be assigned to the zone
(zonecfg:set limitpriv=default,dtrace_proc,dtrace_user). Kernel tracing,
and the tracing of processes in the global zone, remains excluded. DTrace within a zone is of interest
especially for those use cases where a zone is used for software development or where the
administration of a zone was delegated. In this case, the local zone administrator is able to analyze
independent of the platforms administrator.
57