+1.
All articles I've read (think most of them were already mentioned in this
thread) are very sketchy. And even if one studies all man pages linked to
smf(5) pp. one gets at least a clue but not really an in-depth understanding.
The first thing I would like to see is an in-depth explaination of the
manifest aka service_bundle.dtd element and how the elements play together
(get the real picture) and if possible some real use cases for a better
understanding. Often the comment in the DTD are a little bit too abstract.
E.g. the service element allows several elements, which are allowed in the
instance element as well. But nowhere is documented, if on defines e.g.
a dependency in the service element, whether it has an influence on or gets
inherited to the instance elements. Or whether dependency elements in the
instance element replace all dependencies defined in the service element,
or whether the "default?" dependencies from the service element are added
to the dependencies of the instance...
Also a little bit more information wrt. to the dependency and dependent
elements would be nice...
Or AFAIK one is able to set/modify property values for a service via svccfg.
This leads to the question: Is it possible to use the property value in
other elements (and if so, howto)? Consider this simple (ant style) thing:
<property name="configfile" value="/etc/myapp.conf"/>
<dependency name='config' grouping='require_all' type='path'>
<service_fmri value='${configfile}'/>
</dependency>
<exec_method type='method' name='inetd_start' exec='/usr/sbin/myapp -c
${configfile}'/>
...
Regards,
jens.
This message posted from opensolaris.org
