Coy Hile wrote: > I know that when putting together my own manifests, I've been able to use the > "dependency" configuration to say that my service depends upon some other as > well as (IIRC) "dependent" to say that some other service is dependent upon > my own. (Eg, if I wanted ssh to be dependent upon some service I'd written, I > would list ssh as a dependent in my own manifest rather than changing ssh's > manifest lest it be overwritten by a patch.) > > My question is thus: Is it possible (via svccfg) to add a 'dependent' stanza > to an existing SUNW-provided manifest and have it be persistent through > patches? In this particular case, I'd like to have network/ssh (and SRSS if > I ever change that to run via SMF rather than init scripts) be dependent upon > zones being up and running as my KDCs are in local zones. > > Thanks, > > -Coy > > > Coy,
If I understand correctly, you want to define extra dependents to system/zones for ssh and SRSS. I believe such user customization will persist through patches(unless the patch removes/obsoletes the service). However, what you want to wouldn't work for two reasons: 1. a running system/zones service indicates that zones can be autobooted. So you can have an 'online' system/zones while not having any non-global zones. 2. placing dependency on systems/zones for ssh creates a circular dependency error. system/zones has a dependency on multi-user which has a dependency on ssh. Making ssh dependent on system/zones will result in circular dependency. -tony
