Mike,
> I'm working with Intel to answer your questions. Essentially we want to
> provide the least amount of access possible for this daemon to do its
> job.
IIRC, my initial question had 3 parts: How does the project meet
the SMF requirement for authorizations to manage? What is the
Method Context used to start the service? The service is to be
enabled only on the xxx platform - how is this done?
I'd like to clarify the first part about authorizations. When
we talked I may not have been complete.
If there are no properties that configure the service as in
a property group of type application, there is no need for
value authorizations to manage them.
If the service is never intended to be enabled/disabled by
the administrator (but always enabled/started automatically
at boot time and never disabled), there is no need for
action/value authorizations to manage the service.
If both are true and there is no need for defining authorizations
for the service, there is no need for a service related
Rights Profile.
HTH,
Gary..
>
> For starting the daemon, I'm guessing that we'll have to create
> something similar to
> usr/src/cmd/svc/profile/platform_SUNW,SPARC-Enterprise.xml
> for these x86 machines since we want the service to be enabled by
> default on the platforms that support it. Does anyone have any
> recommendation about who to talk to about how to get this done?
>
> Thanks,
>
> Mike
>
> On Tue, 2009-10-13 at 13:29 -0700, Gary Winiger wrote:
> > > The acpihpd is started and stopped using the standard Solaris service
> > > management facility. The acpihpd is an smf service, and will only be
> > > enabled on
> > > the platforms which supports IOH/CPU/memory hot plug.
> >
> > How is the SMF usage policy met?
> > http://opensolaris.org/os/community/arc/policies/SMF-policy
> > Specifically the authorizations, what Rights Profile the authorizations
> > will be contained in, method context, ...
> >
> > How will this be enabled? Is it enabled from platform.xml?
> >
> > Gary..
>
>
>
