Cynthia Eastham wrote: > Lets say I have two services (serviceA and serviceB). ServiceA is > enabled > through an administrative command (not through a profile) while > ServiceB is > enabled through the generic_open profile (disabled through > generic_limited). > > I'd like the following to occur: > 1) If running with the generic_limited profile, > serviceB should be disabled (even if serviceA is enabled) > 1) If serviceA is disabled, > then disable serviceB > 3) If serviceA is enabled, > then enable serviceB iff running with generic_open profile > 3) If serviceA is in a state other than enabled/disabled, > then serviceB should be either offline (running with > generic_open profile) or disabled (running with > generic_limited > profile) > > How do I make this happen? Sounds like an RFE for a new dependency option :^) Another workaround I can think of is to have start method script to check whether serviceA is enabled before invoking the daemon. If serviceA is in 'disabled' state, serviceB should temporarily disable itself. This may work for the specific CR but probably not a good general solution. > > Currently with the way SMF works, if serviceA is disabled, the > serviceB will > believe serviceA to have faulted and will be left in the offline state. > > What I'd like to see is serviceB enabled if and only if serviceA is > enabled > and we are running with the generic_open profile. > > It would be really nice to add a flag be added to a dependency to say > "hey, > if serviceA is disabled, then that's ok, I (serviceB) want to be > disabled too" > rather than "hey, if serviceA is disabled, something bad has gone > wrong and > I (serviceB) can't start". RFE? > > For those interested in the particulars, I'm working on the solution > for CR 5100134 print/rfc1179 ends up by default in "offline" state. I see that disabling print/rfc1179 by default and enabling via lpadmin is a good solution.
-tony
