Umm, that service requires no initialization (as per man page)... something 
else is wrong.

btw, service-fmri means service "uri" eg. svc:/network/rpc/smserver:default

For smserver, we can see the status using:

mritun at spot ~% svcs -l smserver 
fmri         svc:/network/rpc/smserver:default
name         removable media management
enabled      true
state        online
next_state   none
state_time   Sun May 25 14:18:04 2008
restarter    svc:/network/inetd:default
dependency   require_all/restart svc:/network/rpc/bind (online)

The "restarter" as reported above is "svc:/network/inetd:default". So lets 
check it:

mritun at spot ~% svcs -x svc:/network/inetd:default
svc:/network/inetd:default (inetd)
 State: online since Sun May 25 14:18:02 2008
   See: inetd(1M)
   See: /var/svc/log/network-inetd:default.log
Impact: None.

For your case it seems inetd is not running. You can check log file given above 
(/var/svc/log/network-inetd:default.log) to see what is wrong. May be 
hostname/IP isn't configured... but that would be strange.

I remember something like that happening during very early time when I started 
playing with osol. I think while intending to unplumb an nic I unplumbed all of 
them (ifconfig -a unplumb). This had the unintended effect of even unplumbing 
the loopback interface (lo0) and caused every thing thats depends on network to 
fail left and right on next boot. Fixed it by plumbing the loopback interface 
again.
 
 
This message posted from opensolaris.org

Reply via email to