> >> Additionally this case seems not to follow the SMF policy for
> >> configuring properties. See
> >> http://sac.eng.sun.com/cgi-bin/bp.cgi?NAME=SMF.bp
> >> (there is an opensolsaris.org equivalent, but that website is
> >> not presently responding so I can't cut a paste the url).
> >> See appendix D relative to value_authorization.
> >
> >
> > Ok - let me look through this and get back.
>
> Ah - ok - I see what you mean now. I've added the following authorizations
> for
> configuring the service properties for the two daemons, respectively:
>
> solaris.smf.value.smtp-notify
> solaris.smf.value.snmp-notify
You've answered my issues. And as commented at today's PSARC
meeting, uid 0 and all privs is (unfortunately) required by the
underlying channel initialization infrastructure.
> I've added these two authorizations to the "Event Notification Agent
> Management"
> profile (which also encapsulates the manage authorizations for these two
> daemons)
>
> I've also made the appropriate modifications to the service manifests.
+1
Gary..
