My understanding is that create_default_instance is used on single instance service and it simply creates a default instance which has no difference from the service in term of configuration. it equivalent to <instance_name='default'...> </instance>. The non default instance_name starts instance with definition defined in <instance_name></instance> block. <single_instance> is an optional property and allows when is set only one instance to transition to online at any time. I have seen different combinations of <create_default_instance> and <single_instance> in the existing manifests. Some have only <create_...>, some have only <single_instance> and some have both of them, but I think they all mean the same thing - single instance service.
Steve Christine Tran wrote: > Jordan Brown (Sun) wrote: > >> How is >> <create_default_instance enabled="..."/> >> different from >> <instance name="default" enabled="..."/> >> ? >> > > I had this in my notes: > > print/server.xml has: > <single_instance /> > <instance name='default' enabled='false' /> > > Which is different from rarp.xml, which has > <single_instance/> > <create_default_instance enabled='false' /> > > Is this functionally different? > > Slightly: create_default_instance will create the general/package > property if $PKGINST is set. > > > >> I understand that you can do more with <instance>; my question is how >> the trivial case of <instance> is different. >> >> Also: >> >> What does >> <single_instance/> >> really do? >> > > Don't know about that one. > > CT > _______________________________________________ > smf-discuss mailing list > smf-discuss at opensolaris.org >
