What confuses me on this one is that I should be able to disable rpc/meta and mdmonitor should come online fine. It does. But something keeps reenabling rpc/meta at boot! Any idea what that might be?
# svcs -xv svc:/network/rpc/bind:default (RPC bindings) State: disabled since Fri Sep 15 12:42:02 2006 Reason: Disabled by an administrator. See: http://sun.com/msg/SMF-8000-05 See: man -M /usr/share/man -s 1M rpcbind Impact: 5 dependent services are not running: svc:/network/rpc/meta:default svc:/system/mdmonitor:default svc:/milestone/multi-user:default svc:/milestone/multi-user-server:default svc:/system/zones:default # svcadm disable rpc/meta # svcs -xv # init 6 ... # svcs -xv svc:/network/rpc/bind:default (RPC bindings) State: disabled since Fri Sep 15 12:49:41 2006 Reason: Disabled by an administrator. See: http://sun.com/msg/SMF-8000-05 See: man -M /usr/share/man -s 1M rpcbind Impact: 1 dependent service is not running: svc:/network/rpc/meta:default # svcs -l rpc/meta fmri svc:/network/rpc/meta:default name SVM remote metaset services enabled true state offline next_state none state_time Fri Sep 15 12:50:40 2006 restarter svc:/network/inetd:default dependency require_all/restart svc:/network/rpc/bind (disabled) and after another reboot mdmonitor and the rest fail to come up again. How can I track what enables a service? - mo This message posted from opensolaris.org
