http://defect.opensolaris.org/bz/show_bug.cgi?id=12079
--- Comment #15 from Calum Benson <calum.benson at sun.com> 2009-11-11 16:01:33 UTC --- (In reply to comment #14) > For priority group, depends on that group mode, e.g. if the group is 'all must > enabled', then any NCU not in 'online' will result an Orange icon. Ok. > > Red: NWAM daemon is not running. > Or anything cause failures when invoking nwam functions. Ok, so I hadn't really considered that possibility -- what kind of failures can occur that we'd need to indicate in this way? > Agree. My another concern is neither ui spec nor this alias mentions how ENM > state affects panel icon. Thought we don't show users any ENM info (expect the > name of menuitem), it still may be good to include that. The current > implementation is to show orange if any ENM is in 'need attention', show greed > for other state. That's a good point. I'm not sure we should try and modify the icon even further when an ENM is running, as that could get messy. But for now, I guess we could at least show any pertinent ENM status in the icon tooltip. It's also true that we didn't really consider what to do in the GUI when ENMs don't behave as expected. I think it's probably too late to do anything very useful about that for Phase 1, but it would probably be good to file a separate bug so we can address it in a future release. > I don't like to provide a button for restart (or refresh clear) nwam SMF. If > we > are using auto-magic, why we have to consider such case? Red is more like a > bug > to me instead of showing nwamd state. Diagnostic options only make senses if > we > are not using auto-magic. I'm inclined to agree, which is why I wondered in comment #6 if we should even show the icon at all while NWAM isn't running. To me, that seems like the safest thing to do, as it prevents the user trying to interact with something which, at best, isn't going to have any immediate effect. -- Configure bugmail: http://defect.opensolaris.org/bz/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
