On Tue, Mar 03, 2009 at 03:03:21PM -0500, Anurag S. Maskey wrote: > Should a user be allowed to destroy an active/enabled location or ENM > using nwamcfg? I think this should be fine. We call the _fini_event() > which disables the the location or ENM. For locations, when the active > location is disabled, conditions check is triggered and a new location > actived.
Hmm. This seems like one of those cases where we either annoy users who know what they're doing (by forcing them to deactivate a location before destroying it) or we allow users who don't to stumble into a weird state (by allowing them to destroy the active location and thus have possibly unintended results from the destroy operation). I tend to err on the side of trying to prevent confusion, so I would lean toward not allowing users to destroy the active location. > What about NCUs and NCPs? Only "User" NCP and its NCUs can be > destroyed. Should this allowed if the User NCP is active? If so, then > we divert to the Automatic NCP. Same argument applies here. I think the behavior should be the same for both locations and NCPs, and would prefer not allowing active profiles to be destroyed. -renee
