[smf-discuss] nis/server disabled but not re-enabled after svc:/system/sysidtool:system

[Chad Mynhier]

Question:  How do you automatically enable nis/server if doing it via
site.xml doesn't actually achieve what you would expect?

Problem:  After a jumpstart using a flash archive, nis/server is
enabled via site.xml, immediately disabled by
svc:/system/sysidtool:system via these lines in
/lib/svc/method/sysidtool-system:

        if [ -x /usr/sbin/svccfg ] ; then
                if [ -f /var/svc/profile/ns_none.xml ] ; then
                        /usr/sbin/svccfg apply /var/svc/profile/ns_none.xml \
                                >/dev/null 2>&1
                fi
        fi

and is not then re-enabled.  The same disable happens to nis/client,
but nis/client is then re-enabled because
/lib/svc/method/sysidtool-system does the following immediately
afterwards:

        if [ -x /usr/sbin/sysidns ]
        then
                /usr/sbin/sysidns > /dev/console < /dev/console 2>&1
        fi

        #
        # Now apply the name service profile that was just selected
        # during sysidns.
        #
        if [ -x /usr/sbin/svccfg ] ; then
                if [ -f /var/svc/profile/name_service.xml ] ; then
                        /usr/sbin/svccfg apply \
                                /var/svc/profile/name_service.xml \
                                >/dev/null 2>&1
                fi
        fi

and /var/svc/profile/name_service.xml enables nis/client. 
Unfortunately, it says nothing about nis/server.

So, how do you automatically enable nis/server if doing it via
site.xml doesn't actually achieve what you would expect?

I could create another service that depends on
svc:/system/sysidtool:system that re-applies site.xml, but I'd rather
not add a service to handle something that happens once in a server's
lifetime.

Thanks,
Chad Mynhier