Yes, that is what I thought. I think it is too esoteric. An importance
of a zone states in an SNMP monitoring environment is it is either
"running" or not. States such as "ready", or "installed" mean the zone
is not running. If a zone is a server, there is an SNMP process that
can be easily implemented to identify that the server is up or down?.
Once that status is changed then the troubleshooting gets into solving
the issue with "/usr/sbin/zoneadm list -vi" from the global zone.|
i- for installed
Peter Memishian wrote:
> So here are my questions: > > - Do you think this is useful? > > - Do you think the log level (Info) is right? daemon.info is > *not* logged by default, whereas notice is. (So basically: do > you want these messages in /var/adm/messages by default, or not?) > > - Do you think the facility of 'daemon' is OK? With Solaris > syslog you can't AFAIK route messages based on the value of > 'program' (which in this case is 'zoneadmd'). > > - Any comment about whether the info provided is sufficient? > For example, when a zone reboots it goes through numerous > state transitions, but I chose to express this as one > big transition-- does that work for everyone?Encouraging programmatic use of syslog seems a step in the wrong direction to me. Surely we can provide a better mechanism to notify them of state changes?
_______________________________________________ zones-discuss mailing list email@example.com