http://defect.opensolaris.org/bz/show_bug.cgi?id=10123
--- Comment #3 from Anurag S. Maskey <Anurag.Maskey at Sun.COM> 2009-09-08 16:32:00 UTC --- Investigating a bit further, the chain of events are correct. nwamd receives two actions via libnwam. 1. When the location is disabled, the "enabled" property is set to false and on commit of this change, libnwam asks nwamd to re-read (refresh) the location. 2. Then, libnwam sends the disable action to nwamd. Action 1 causes following state changes: > OBJECT_ACTION loc foo -> action refresh > > OBJECT_STATE loc foo -> state offline*, method/service enable > execut > OBJECT_STATE loc foo -> state online, active > Action 2 causes the remaining state changes. > OBJECT_ACTION loc foo -> action disable > > OBJECT_STATE loc foo -> state online*, disabled by administrator > > OBJECT_STATE loc foo -> state disabled, disabled by administrator > > OBJECT_STATE loc Automatic -> state offline*, method/service > enable > OBJECT_STATE loc foo -> state disabled, disabled by administrator > > OBJECT_STATE loc Automatic -> state online, active > Because of the asynchronous handling of events, the two actions get intertwined in nwamd and produces the state changes shown in the description and comment 2. -- 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.
