Alan, When a dependency is re-evaluated depends on the 'restart_on' value for that dependency. All dependencies of milestone/name-services have restart_on='none'. For the behavior you're expecting, you should have set restart_on='refresh'. With that said. I am *not* saying that the restart_on value for those dependencies should be changed from 'none'. I am just trying to explain the reasoning why the dependencies of milestone/name-services are not being re-evaluated.
Antonello Alan Maguire wrote: > hi folks > > Quick question about milestone behaviour, specifically > as it relates to a milestone's dependencies. > > In looking at an issue with autofs and nameservices, > I've been trying to understand how the name-services > milestone behaves. The name-services milestone depends on > the various specific name services (nis, nisplus, dns and > ldap), each with an optional_all dependency. This form of > dependency means that the service we depend on needs to > be online or disabled for that dependency to be satisfied > AFAIK. So, for example, the name-services milestone can > be reached if no specific name services are enabled, or if > one is and is online, etc. So far so good. > > What I'm confused about is that the milestone > doesn't seem to notice when a service that it depends > on later moves offline. If it were a normal service, this > would trigger it to go offline I would have thought, but > milestones don't seem to work that way. What's the > reasoning here? > > Thanks! > > Alan > _______________________________________________ > smf-discuss mailing list > smf-discuss at opensolaris.org
