I am sponsoring this fasttrack for Tony Nguyen. We believe it qualifies as closed approved automatic, as it makes minor clarifications only to an existing policy.
Note that I have set this to be an externally visible case, with mail to psarc-ext at sun.com. For those of you on smf-discuss at opensolaris.org, this is a primarily informative mail. If you have specific comments about the changes being made, feel free to raise them in this thread. If you have comments or questions not specifically related to the change proposed in this case, please remove the psarc-ext alias from the cc list, and change the Subject line before responding. liane --- Clarification to SMF Policy Tony Nguyen 08 February 2007 1. Summary This cases proposes to make some simple clarifications to the SMF Policy: http://opensolaris.org/os/community/arc/policies/SMF-policy/ These modifications simply clarify existing policy, and are made based on feedback from consumers of the policy. As no interface nor architectural changes are made, we are filing this case as a self-reviewed Closed Approved Automatic fasttrack. 2. Policy changes --- SMF.bp Thu Feb 8 11:03:30 2007 +++ SMF-new.bp Thu Feb 8 11:08:57 2007 @@ -81,7 +81,8 @@ </p><ul> <li> Criteria to determine when a project must deliver SMF services <li> Migration of "legacy" (existing) services to SMF - <li> Requirements for delivery of SMF services + <li> Requirements for delivery of SMF services (for any + restarter, including svc.startd and inetd) <li> Requirements for delivery of new system and system service configuration </ul> @@ -129,7 +130,9 @@ # within this document? How can a project determine # whether this policy applies to them? Scope = - This policy applies to you if you create, modify or use + This policy applies to you if you create or modify SMF + services (for any restarter, including svc.startd and inetd). + This policy also applies to you if you create, modify or use files in any of these locations: <ul> <li> /etc/init.d and rc?.d scripts @@ -328,8 +331,8 @@ is the appropriate repository for their data. </p> - <H5>Appendix C: Guidance for services that must be started early in - the boot sequence</H5> + <H5>Appendix C: Guidance for service instances delivered as + "enabled"</H5> <p> Under most circumstances, service manifests should specify their service instances as "disabled". This decouples the -- Liane Praza, Solaris Kernel Development liane.praza at sun.com - http://blogs.sun.com/lianep
