> Would there every be a reason to write a service manifest and not > have it create a instance when you import it?
A good reason for doing this is because you want to take advantage of the relationship between the service and the instance. The primary element of this relationship is the fact that instances inherit properties from services, and you can have multiple instances per service. One possible application of this split is a service which defines all the defaults and creates instances as-needed to fulfill some need. For example, svc:/network/ssl/proxy defines a set of defaults for a Kernel SSL service, and ksslcfg dynamically creates instances when new SSL servers are desired. No SSL server is needed out-of-the-box, so the service ships with no instances. Dave
