hi folks i've noticed a timing problem on some systems with the newly-introduced routing-setup service, introduced by my putback of 6312914 (routeadm needs to support smf-based routing services). the service runs "routeadm -u", which now interacts with SMF-based routing services, and on first boot post-upgrade, if these have not been imported by manifest-import yet, the command fails and routing configuration may not be upgraded correctly. would a simple optional_all dependency on manifest-import suffice here? my concern is that in cases where large numbers of manifests are imported, no routes would be available until the process has completed. any help is greatly appreciated! thanks!
alan This message posted from opensolaris.org
