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. > > Now imagine that you are new to Solaris and are working for the first time > with SMF. I'll admit that SMF doesn't necessarily have the greatest curb appeal. On the other hand, what it delivers in terms of long term ease of use, simplified clustering application, sophistication of the boot process, visibility of service states, easy integration with resource management and role based access control more than make up for the first 30 minutes spent with it. > The first thing I would think is: Solaris has all these commands why don't > they have a > command that can easily display this kind of information? Why do I need to > bother > about the difference in service properties? Didn't someone contribute an SMF service log finder a while ago (trolls looking for restarter/logfile and then back to the restarter itself) ? That's the beauty of OpenSolaris and the community - if you think this would help then contribute such a script. I'm sure others would appreciate your efforts. And in looking the glass half full :-) Isn't it really cool that you only have one command to start or stop a service and you don't have to look through several configuration files just to determine if it is a standalone daemon or an on demand service via a delegated restarter ? In other words, the start and stop methods are now configuration artifacts and not major points of administration. Now that's cool. Bob
