I'm an SMF novice, but here's what I was able to glean from the manuals
and some examples[1]:
The pkg.depot SMF service manifest has the declaration:
<single_instance/>
in it. Also, the pkg property_group is declared within the <service>
tag, not within an <instance> tag. This means that there can only be
one service instance ("default") and that these properties can only be
set at the service level.
To support multiple pkg.depot instances, the <single_instance/>
declaration would need to be removed and replaced with instance
declarations that look like this:
<instance name='instance1' enabled='false'>
<property_group name='pkg' type='application>
<propval name='port' type='count' value='80' />
<propval name='inst_root' type='astring' value='/var/pkg/repo' />
<propval name='socket_timeout' type='count' value='60' />
<propval name='threads' type='count' value='10' />
</property_group>
</instance>
Then one would be able to set these values at a per-instance level.
Here is an updated webrev for these changes:
http://cr.opensolaris.org/~tmueller/cr-2309,2310-2/
Thanks.
Tom
[1] http://www.sun.com/software/solaris/howtoguides/smfmanifesthowto.jsp
Danek Duvall wrote:
> On Wed, Jun 25, 2008 at 10:31:04AM -0500, Tom Mueller (pkg-discuss) wrote:
>
>
>> Webrev: http://cr.opensolaris.org/~tmueller/cr-2309,2310/
>>
>
> Hm. It's odd that setting pkg/port on a specific instance fails. I wonder
> if this is a bug in our manifest? Perhaps an SMF expert could comment on
> that aspect? Basically,
>
> svccfg -s application/pkg/server:default setprop pkg/port = 9999
>
> fails with "svccfg: No such property group "pkg".". Drop ":default", and
> it works. But shouldn't we be able to set the property per-instance?
>
> Or am I just totally confused?
>
> Danek
>
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
