Should a SMF service be enabling an administratively disabled service ? Specifically, svc:/network/routing-setup:default re-enables the following services each time the system is booted:
svc:/network/routing/ndp:default svc:/network/routing/route:default This extract from the method script suggests its doing this when it thinks the system has been upgraded, which means this might happen once, but these services get re-enabled each boot (or restart or svc:/network/routing-setup:default): # # If routing.conf file is in place, and has not already been read in # by previous invokation of routeadm, legacy configuration is upgraded # by this call to "routeadm -u". This call is also needed when # a /var/svc/profile/upgrade file is found, as it may contain routeadm commands # which need to be applied. Finally, routeadm starts in.ndpd by # enabling the ndp service (in.ndpd), which is required for IPv6 address # autoconfiguration. It would be nice if we could do this in # network/loopback, but since the SMF backend is read-only at that # point in boot, we cannot. # /sbin/routeadm -u BTW neither /var/svc/profile/upgrade or /etc/inet/routing.conf exist. This is a newly installed system. Thanks Mark
