On Tue, 2010-03-09 at 18:02 +, Brandon High wrote:
> The instance runs as zfssnap and the user *should* be able to change
> values in smf, right?
Yes - I think that's a bug - it looks like the SMF zfs/ propgroup should
have value_authorization set as well.
You can workaround this by doing:
#
On Mon, Mar 8, 2010 at 1:47 PM, Tim Foster wrote:
> Looking at the errors, it looks like SMF isn't exporting the values for
> action_authorization or value_authorization in the SMF manifest it
> produces, resulting the service not being allowed to set values in
> svccfg when it runs as 'zfssnap'.
(Subscribing to the zfs-auto-snapshot list to avoid moderation hold.)
On Mon, Mar 8, 2010 at 1:47 PM, Tim Foster wrote:
> I usually add SMF instances using 'svccfg -s add myinstance'
I tried that, but there that doesn't create/copy the property groups.
Do I have to manually duplicate the settin
I hit the wrong button when moderating the post to zfs-auto-snapshot@
mailing list. I'm forwarding the original mail from Brandon below.
Summarising Brandon's questions:
* how to best create SMF instances on an existing service
* why are there permission errors when running a new instance creat
