Quoth Alan Maguire on Sat, Nov 04, 2006 at 07:12:12AM -0800: > 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.
So you're saying that routing-setup is imported by manifest-import and immediately started, and routeadm -u tries to set properties in other routing services, but if manifest-import hasn't reached those other routing service manifests yet, then the services won't exist in the repository and routeadm -u will fail? > 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! Well manifest-import should always be enabled, so routing-setup would always wait for it. Does routing-setup actually install routes? When were routes available before your changes? David
