----- Original Message ----- From: Bob Netherton <bob.nether...@sun.com> Date: Wednesday, March 7, 2007 4:42 pm Subject: Re: [smf-discuss] Re: SMF annoyance To: Peter van Gemert <peter.van.gemert at accenture.com> Cc: smf-discuss at opensolaris.org
> 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 fine 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 no need to make this more complex then needed. The same for the logfile, why make the admin go do svcs -l, find the logfile and the finally look at the file? I very much like Darren's suggestion of svcs -L (the L is free, no new command to get to know, just a new option). In keeping with this, the methods could be listed using svcs -l This lists things like dependencies etc, so listing the methods here too would be fitting IMHO. So, all in all: yes I would like to have the niceties. Menno
