I am wondering about the logic in how the script identifies specific
versions. It appears that you are looking at /etc/release to define
this.  This seems to limit some features of your script because I have a
Solaris 10 update 1 system that has been updated to 05/08 (update 5) but
/etc/release still reflects update 1 (updated using 05/08 patch bundle).

I am using CPU caps but your tool doesn't recognize that I have that
feature available. Since these features really come from the kernel
version, would that be a better way to identify release version in your
script; Just a thought.

In the meantime I tricked the script to think I am on update 5 and I am
getting better results.

-= Kevin =-

-----Original Message-----
From: Jeff Victor [mailto:[EMAIL PROTECTED] 
Sent: Monday, November 10, 2008 9:01 AM
To: Young, Kevin
Subject: Re: [zones-discuss] Zone Statistics: monitoring resource use of

On Mon, Nov 10, 2008 at 11:21 AM, Young, Kevin <[EMAIL PROTECTED]>
> I am curious if you have plans to make it Solaris 10 compatible.

I do all development on Solaris 10. The script makes an effort to
distinguish between the different capabilities of the different
Solaris 10 updates.

> -----Original Message-----
[mailto:[EMAIL PROTECTED] On Behalf Of Jeff Victor
> Sent: Sunday, November 09, 2008 5:54 PM
> To:
> Subject: [zones-discuss] Zone Statistics: monitoring resource use of
> It has become clear that there is a need to monitor resource
> consumption of workloads in zones, and an easy method to compare
> consumption to resource controls. In order to understand how a
> software tool could fulfill this need, I created an OpenSolaris
> project and a prototype to get started. If this sounds interesting,
> you can find the project and Perl script at:
> .
> If you have any comments, or suggestions for improvement, please let
> me know on this e-mail list or via private e-mail.


zones-discuss mailing list

Reply via email to