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? > > 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.
Well, I don't think there's anything that ties dependencies together in terms of which profile enabled the service. > > 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? What's functionally wrong with this method? offline is functionally the same as disabled, OK except for the annoying message when you do svcs -x. When serviceA is restarted, its offlined dependents restart. I thought there was a CR to make svcadm act on a group of services, but I just looked and it's only to act on multiple instances ... hmmm. > For those interested in the particulars, I'm working on the solution for > CR 5100134 print/rfc1179 ends up by default in "offline" state. > > Cindy
