On Wed, 14 Mar 2007, Steven Sim wrote: > Gurus; > > An attempt to enable the telnet service using svcadm failed with the following > messages... > > Mar 14 12:21:47 inetd[251]: Property 'name' of instance > svc:/network/rpc/rstat:default is missing, inconsistent or invalid > Mar 14 12:21:47 inetd[251]: Invalid configuration for instance > svc:/network/rpc/rstat:default, placing in maintenance > Mar 14 12:21:47 inetd[251]: Property 'name' of instance > svc:/network/telnet:default is missing, inconsistent or invalid > Mar 14 12:21:47 inetd[251]: Property 'proto' of instance > svc:/network/telnet:default is missing, inconsistent or invalid > Mar 14 12:21:47 inetd[251]: Invalid configuration for instance > svc:/network/telnet:default, placing in maintenance > Mar 14 12:21:48 svc.startd[7]: svc:/system/mdmonitor:default: Method > "/lib/svc/method/svc-mdmonitor" failed with exit status 1. > What was even more interesting was the output from svcs -vx telnet:default > which > basically stated that the "restarted failed with no explanation"
It's not directly SMF I recall. Check your /etc/services, and see if there is a telnet entry. [sec-b1600-10/root] cp /etc/services /etc/services.ok [sec-b1600-10/root] rm /etc/services [sec-b1600-10/root] svcadm enable telnet Mar 13 21:51:34 sec-b1600-10 inetd[16563]: Property 'name' of instance svc:/network/telnet:default is missing, inconsistent or invalid Mar 13 21:51:34 sec-b1600-10 inetd[16563]: Property 'proto' of instance svc:/network/telnet:default is missing, inconsistent or invalid Mar 13 21:51:34 sec-b1600-10 inetd[16563]: Invalid configuration for instance svc:/network/telnet:default, placing in maintenance [sec-b1600-10/root] Plus, don't run telnet anyways. -- Dave
