Hi Joe,
On 04/15/09 16:35, Joseph J VLcek wrote: > Jan, > > Thanks for looking into this and the great description! You are welcome :-) > > Please forgive me if my perspective is not correct. I'm learning how > this works as I go. > > Until the existing design can be reworked, it seems to me a safer > approach might be to not allow a consecutive invocation of "installadm > create-service" on SPARC. > > If a SPARC user issues "installadm create-service" and a service is > already created issue an error message that only one service is > currently allowed on SPARC and "installadm delete-service" must be run > prior to creating a second service. > > OK I can imagine this is not flexible for customers but it might be a > safe approach to help avoid customer problems/confusion until the > design can be reworked. > > Again I apologies if my perspective is naive. I'm just thinking here > and trying to help. I think this is definitely one of possibilities we should consider. In general I think only set of features which is solid and stable should be released, otherwise we will be seeing bugs filed for side effects of scenarios which could lead to the type of problems described in 8130. Thanks s lot ! Jan
