Cathy Zhou wrote: > Darren.Reed at Sun.COM wrote: >> Cathy Zhou wrote: >> >>> Hi, >>> >>> I have question regarding the interaction of SMF and zones, and would >>> like to get some help here: >>> >>> As part of my project (the Clearview vanity naming project), I added >>> a service network/linkmgmt to manage datalinks, and I changed >>> manifest of two services (device-local and network/physical) to make >>> them depends on the new service. Note that this linkmgmt service is >>> only needed in the global zone. >>> >>> It works fine on the global zone. But in a local zone, >>> network/physical failed to start because linkmgmt is not correctly >>> started: >>> >>> # svcs -l network/physical >>> fmri svc:/network/physical:default >>> name physical network interfaces >>> enabled true >>> state offline >>> next_state none >>> state_time Tue Apr 17 02:46:17 2007 >>> restarter svc:/system/svc/restarter:default >>> dependency require_all/none svc:/network/loopback (online) >>> dependency require_all/restart svc:/network/linkmgmtd (maintenance) >>> >>> But how can I indicate that to not start linkmgmt in a local zone, >>> and the two above services doesn't have to check the dependency on it? >> >> >> I suppose changing the limkmgmt service to be a "do nothing" service >> for local zones (so it can be enabled everywhere) is out of the question? >> > We could do that, Christine Tran gave me the same suggestion. But I am > just wondering if there is any cleaner way, and how this is done for > other services. For example, system/sysevent only exists in the global > zone, and there are services depend on it (for example, > milestone/single-user) does not seem to be depend on it in the local zone. >
That's because the dependency of the milestone is actually expressed by a <dependent> tag in the service's manifest, and since it's not installed in the non-global zone, it's therefore not present as a dependency of the milestone there. Dave
