since it seems it''s not actually possible to run dtrace on a local zone on solaris 10 (AFAIK it''s possible only on latest solaris express builds), i wonder: is there a way to know, by executing a dtrace script on a solaris 10 global zone, in what zone was running the process that fired a probe? also, is it possible to use a predicate to allow a probe to be fired only when the process comes from a specific local zone?
There is a "zonename" built-in variable. (It''s not in the guide, so I''m not sure which release it was introduced.) Chip Alessio Cervellin wrote:> since it seems it''s not actually possible to run dtrace on a local > zone on solaris 10 (AFAIK it''s possible only on latest solaris express > builds), i wonder: is there a way to know, by executing a dtrace > script on a solaris 10 global zone, in what zone was running the > process that fired a probe? > also, is it possible to use a predicate to allow a probe to be fired > only when the process comes from a specific local zone? > _______________________________________________ > dtrace-discuss mailing list > dtrace-discuss at opensolaris.org
Hi all, I''ve been using "zonenames" a lot because we use zones a lot in my production servers but it never crossed me that its not in the docs. Anyway, I am pretty lost tracking changes/additions to DTrace. Is there any sits tracking this? If not, can we have a page at the community site for tracking the changes and additions? -- Just me, Wire ... On 6/9/06, Chip Bennett <cbennett at laurustech.com> wrote:> There is a "zonename" built-in variable. (It''s not in the guide, so I''m > not sure which release it was introduced.) > > Chip > > Alessio Cervellin wrote: > > > since it seems it''s not actually possible to run dtrace on a local > > zone on solaris 10 (AFAIK it''s possible only on latest solaris express > > builds), i wonder: is there a way to know, by executing a dtrace > > script on a solaris 10 global zone, in what zone was running the > > process that fired a probe? > > also, is it possible to use a predicate to allow a probe to be fired > > only when the process comes from a specific local zone? > > _______________________________________________ > > dtrace-discuss mailing list > > dtrace-discuss at opensolaris.org > > > _______________________________________________ > dtrace-discuss mailing list > dtrace-discuss at opensolaris.org >
> There is a "zonename" built-in variable. (It''s not in the guide, so I''m not > sure which release it was introduced.)It was first supported in Solaris 10 3/05 although it was made available through Solaris Express before that. I was surprised to see that you''re right - the "zonename" variable is missing from the Dynamic Tracing Guide. I''ve filed 6436567 DTrace guide is missing description of "zonename" variable to have this fixed. Thanks for bringing it to our attention. dsc