lianep at eng.sun.com wrote: >Menno Lageman writes: > > >>From: Bob Netherton <Bob.Netherton at Sun.COM> >> >> >>>On Wed, 2007-03-07 at 07:08 -0800, Peter van Gemert wrote: >>> >>> >>>># svcprop -p start/exec telnet >>>>svcprop: Couldn't find property group `start' for instance >>>> >>>> >>>`svc:/network/telnet:default'.> >>> >>> >>>>The inetd managed services use another property >>>># svcprop -p inetd_start/exec telnet >>>>/usr/sbin/in.telnetd >>>> >>>> >>>This is because inetd is the delegated restarter for telnet. inetd >>>records it's properties elsewhere in the repository. If telnet were >>>started as a standalone daemon then it would have the start/exec >>>property. >>> >>> >>> >>While this is obviously true, should we bother the administrator with this fi >>ne distinction? If he/she wants to find the start/stop method he/she must now >> first know which restarter is responsible for the particular service and the >> issue the approppriate svcprop incantation to get what he/she needs. I see n >>o need to make this more complex then needed. >> >> > >Further complexity lies in the fact that not all restarters are required to >have start/stop methods, and may have any number of methods. (svc.startd >managed services have 3 defined methods now, inetd services have 5.) > >But, I think that's pretty easily overcome. Does it sound helpful for >svcs -l to print the "exec" string of all "method" type property >groups for a service? > >If so, I'll file the RFE. > >
Hmmm, so how to do get the methods would be: svcs -l ssh | egrep '^method' ? That could be nice. What would the output for these lines look like? Darren
