Quoth Cathy Zhou on Sat, Jan 05, 2008 at 12:41:48AM +0800:
> But the reboot after bfu shows that although datalink-management service
> instance is successfully removed, the network-physical still has the
> dependency on the datalink-management service ("svcs -d
> network/physical" does not show that dependency, but svcs -xv output
> shows that the state of the network-physical service instance is now
> offline because "Dependency svc:/network/datalink-management is
> absent". A "svcadm refresh" fixes the problem.
That's strange. I believe svcs -d and svcs -x should both use the
running snapshot. If you can reproduce this, I would like to take
a look.
> Note that before I made the changes described in [1] (see below),
> everything works fine in the global zone. So I guess this is something
> to do with the SVCCFG_REPOSITORY setting I added.
>
> My question is, is the fix we proposed for 6647203 the correct way to
> remove a service (both in global and non-global zone)? If it is not,
> what would be the correct fix?
Well if you're going to use SVCCFG_REPOSITORY, then the
/etc/svc/volatile/repository_door test should be reconsidered. But the
problem seems to be a discrepency between the current properties and the
running snapshot, in which case you need the fix for 5087504, which
requires changes to either svcadm or svc.configd, and is not currently
being worked on.
David
