Darren Reed wrote:
Guys, In most parts of the source code, the zoneid is unsigned,
except for where we use ALL_ZONES. Then in some places,
we assign or expect -1 to be the zoneid, for example in what
psh prints and expects to see.
It would seem that we want the zoneid to be unsigned except
Hello, Jeff!
Have you tried prstat -Z? Is this not what you are looking for?
Best regards,
HeCSa.
http://www.aosug.com.ar
On Fri, Sep 18, 2009 at 10:27 AM, Jeff Victor jeff.j.vic...@gmail.comwrote:
Has anyone written a tool to provide per-zone reporting of CPU usage -
that can be shared? I
On Fri, Sep 18, 2009 at 8:30 AM, Mads Toftum m...@toftum.dk wrote:
On Fri, Sep 18, 2009 at 09:27:54AM -0400, Jeff Victor wrote:
Has anyone written a tool to provide per-zone reporting of CPU usage -
that can be shared? I know someone who wants to do this.
There's
Hernan,
In addition to Mike's point about short-lived processes, prstat
doesn't tell me how much CPU time a process used during its life.
Solaris Accounting will generate a record for each process, showing
how much CPU time it used, and which zone it was in. If you collect
all of the records, you
That's right, there is a key term here, and is reporting, which involves
accounting.
Thanks, Jeff!
Best regards,
HeCSa.
On Fri, Sep 18, 2009 at 1:48 PM, Jeff Victor jeff.j.vic...@gmail.comwrote:
Hernan,
In addition to Mike's point about short-lived processes, prstat
doesn't tell me how
Darren Reed wrote:
James Carlson wrote:
What kind of confusion are you expecting?
If it is an opaque type, then how does it get printed?
You have to use one of the look-up functions to convert it to a string
for printing. Zones are named, not numbered, even in the kernel.
This was a
Darren Reed wrote:
On 18/09/09 10:44 AM, James Carlson wrote:
Darren Reed wrote:
As an unsigned integer for all values, except -1, or as a signed integer?
I still think it's properly neither. Users can't reasonably do
anything with those ephemeral numbers, so printing them (or using
John Leser wrote:
Darren Reed wrote:
Do a man snoop and search for the word zone.
Oh, that was a bit of a let-down...
Anyway, this seems to pose an interesting challenge to programs like
snoop that want to encode zone ID information in output files. The zone
ID numbers are essentially
Do a man snoop and search for the word zone.
My argument wasn't that there were zero bugs in the OS. That keyword
seems to me to be pretty clearly a defect in snoop. (And apparently a
recent one; less than a year old.)
... and indeed, there's a CR open to allow snoop to accept zone
