Hi Mika,
Mika Borner wrote:
> Hi
>
> I have two questions about the SMF Repository:
>
> 1. When reimporting a manifest for a service that is enabled in the
> repository, but is disabled in the manifest (using the instance's
> "enabled='false' "-attribute), the service stays enabled. Is this
> correct behaviour? I have tested, that other values of the service are
> updated (like e.g. method_context values). It seems that service
> states
> are behaving differently.
This is expected behavior. The current service state is stored in the
*volatile* repository. When you re-import your manifest, the updates
will occur in the *persistent* repository. The change in your manifest
will cause the 'enabled' property to be updated not the restarter/state
property (that indicate if the service is online or not). In consequence,
if your service was online before the import, it'll remain online after
after the import. However, if your system reboots after the import,
svc.startd will evaluate the 'enabled' property and won't try to start
your service (because it is set to false).
>
> 2. Manifests that contain the dependent-element, will add a
> dependency-property to its dependent service. While this is certainly
> correct, it generates problems when removing a service that has
> dependents (using the svccfg delete). As a sysadmin I have to
> remember,
> to check all the dependent services, and delete the dependencies not
> needed anymore. This can lead to inconsistencies. Could this be fixed
> in
> the "svccfg delete" subroutine? This would also simplify the removal
> of
> services with pkgrm.
svccfg(1M) says :
delete [-f] {name | fmri | pattern}
The named child of the current selection or the entity
specified by fmri is deleted. Attempts to delete service
instances in the "online" or "degraded" states will fail
unless the -f flag is specified. If a service or service
instance has a "dependents" property group of type
"framework", then for each of its properties with type
"astring" or "fmri", if the property has a single value
which names a service or service instance then the
dependency property group in the indicated service or
service instance with the same name as the property will
be deleted.
So, if your service has dependents svccfg delete should handle them.
Can you be more specific on the problem you encounter when you use
"svccfg delete"?
Thanks
Renaud
>
> Mika
>
> # mv Disclaimer.txt /dev/null
>
>
>
> -------------------------------------------------------------------------
> This message is intended for the addressee only and may
> contain confidential or privileged information. If you
> are not the intended receiver, any disclosure, copying
> to any person or any action taken or omitted to be taken
> in reliance on this e-mail, is prohibited and may be un-
> lawful. You must therefore delete this e-mail.
> Internet communications may not be secure or error-free
> and may contain viruses. They may be subject to possible
> data corruption, accidental or on purpose. This e-mail is
> not and should not be construed as an offer or the
> solicitation of an offer to purchase or subscribe or sell
> or redeem any investments.
> -------------------------------------------------------------------------
>
> _______________________________________________
> smf-discuss mailing list
> smf-discuss at opensolaris.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: renaud.manus.vcf
Type: text/x-vcard
Size: 218 bytes
Desc: not available
URL:
<http://mail.opensolaris.org/pipermail/smf-discuss/attachments/20060825/6b95ea4f/attachment.vcf>
