Dave Miner wrote: > Cathy Zhou wrote: >>>> 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. >>> >> Can I do the same for linkmgmt service (to express the dependencies >> use <dependent> tag in linkmgmt)? How to not install linkmgmt in the >> non-global zone? >> > > Yes, that's likely a good answer if it's truly a global-zone-only > service. How linkmgmt should be handled by zones installation is a > property of its package, governed by the SUNW_PKG_ALLZONES, > SUNW_PKG_HOLLOW, and SUNW_PKG_THISZONE attributes; see pkginfo(4). Most > likely what you're after with this solution would be: > > SUNW_PKG_ALLZONES=true > SUNW_PKG_HOLLOW=true > SUNW_PKG_THISZONE=false > I will try it out. Thanks!
- Cathy
