NWAM Phase 1 will deliver a new manifest for network/physical. After
a user "image-update"s the system, the network/physical manifest must
be imported before network/physical:nwam comes online. Because of
dependencies, manifest-import comes online after network/physical.
If the network/physical manifest isn't imported,
network/physical:nwam goes into maintenance mode (and a host of other
services don't run). This problem is only on the first reboot after
the system is updated.
In Nevada, this problem can be overcome by changing the bfu script or
postinstall script (on SUNWcnetr) to "svccfg import" the new manifest.
What is the approach to solving this problem in OpenSolaris?
Make your start method work w/ the old manifest properties; then no
special upgrade processing is needed. Note that your service can
wait to finish coming on line until manifest-import runs if that's
easier.
NWAM cannot wait for manifest-import to come online because
manifest-import is indirectly dependent on network/physical being online.
The issue is not only with the properties. NWAM has added a new user
that the new nwamd daemon runs as. The current (Phase 0/0.5) nwamd ran
as root, while the Phase 1 nwamd must run as netadm user (that NWAM will
add).
Also, the start method of NWAM cannot do a "svccfg import" because the
filesystem is read-only at that time (NWAM runs very early during boot;
filesystem/* services are indirectly dependent on NWAM).
Anurag
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
