spot (of bother) in a zone

I was testing out spot and I was in a zone (non-global). spot does this at the start:

prtdiag can only be run in the global zone

Use of uninitialized value in concatenation (.) or string at /opt/studio12/SUNWspro/bin/spot line 290.

Use of uninitialized value in concatenation (.) or string at /opt/studio12/SUNWspro/bin/spot line 290.

Use of uninitialized value in pattern match (m//) at /opt/studio12/SUNWspro/bin/spot line 292.

Use of uninitialized value in pattern match (m//) at /opt/studio12/SUNWspro/bin/spot line 292.

Use of uninitialized value in pattern match (m//) at /opt/studio12/SUNWspro/bin/spot line 292.

Use of uninitialized value in pattern match (m//) at /opt/studio12/SUNWspro/bin/spot line 292.

Use of uninitialized value in pattern match (m//) at /opt/studio12/SUNWspro/bin/spot line 292.

The rest of the run is fine though, so I assume spot is just finding some system info for its summary.

Will this use of zones be supported in spot?

[1179 byte] By [tony-curtisa] at [2007-11-26 17:07:27]
# 1

spot calls prtdiag to get and display information about the

processor(s). If prtdiag can not be run, spot does not try

to get the information in any other way at this time.

Your feedback and your suggestion for supporting zones

is well taken. We'll put it on our wish list, and look into it.

Thanks,

Peter Farkas

peter.farkasa at 2007-7-8 23:35:16 > top of Java-index,Open Source Technologies,OpenSPARC...