Moritz Willers wrote: > K. Let's change subject as this seems related but is not quite on topic. > > Yes, I suspect that bit of code as well. And I suspect it to be somehow > triggered out of the mdmonitor startup script. > > The system has mirrored root disks and has the metadb replicas that go > with it. That does not imply that I need a running rpc.metad, does it? > I never understood what that daemon does, but the manpage seems to imply > it's there to *remotely* manage disksets. We don't use disksets and we > certainly won't want them to be remotely managed. > > I want a secured system with reduced services - i.e. no rpcbind, no > rpc.metad, and a lot more disabled - but mirrored root disks for > redundancy. Surely that must be possible. Certainly always has been.
Well, we don't do mirrored root disks (we use a different methodology) but we do use other mirrored disks on virtually all of our servers including metadb replicas. And I see: Data: disabled Mar_24 svc:/network/rpc/mdcomm:default Data: disabled Mar_24 svc:/network/rpc/metamed:default Data: disabled Mar_24 svc:/network/rpc/metamh:default Data: disabled Mar_24 svc:/network/rpc/meta:default Data: disabled Mar_24 svc:/system/mdmonitor:default Data: online Mar_24 svcs -l So the only thing online is metainit. And it does not change on reboot. Also: Data: disabled Mar_24 svc:/network/rpc/bind:default Maybe mirrored root disks changes things - in which case I am happy we do it differently. :-) HTH, =wb > What in SVM thinks that it needs to enable rpc.metad just because I have > metadb replicas? > > - mo > > > On 15 Sep 2006, at 21:39, Tom Whitten wrote: > >> I think that I missed the original posting on this, so I don't have >> all of >> the context. Nontheless, I'll climb out on the limb and try to answer >> your >> question. :-) >> >> Do you have any metadbs (Solaris Volume Manager replicas) on your system? >> If so, the SVM code is probably enabling the services. See the >> meta_smf_enable function in >> http://cvs.opensolaris.org/source/xref/on/usr/src/lib/lvm/libmeta/common/meta_smf.c. >> >> >> >> tom >> >> Moritz Willers writes: >>> 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 >>> _______________________________________________ >>> smf-discuss mailing list >>> smf-discuss at opensolaris.org > > > ------------------------------------------------------------------------ > > _______________________________________________ > smf-discuss mailing list > smf-discuss at opensolaris.org
