On Mon, Mar 8, 2010 at 1:47 PM, Tim Foster <tim.fos...@sun.com> 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'.
After playing around a bit, I found the right way to verify this: $ svcprop -p general zfs/auto-snapshot:rpool-backup general/action_authorization astring solaris.smf.manage.zfs-auto-snapshot general/value_authorization astring solaris.smf.manage.zfs-auto-snapshot general/enabled boolean true general/entity_stability astring Unstable This is exactly the output that I'm getting for zfs/auto-snapshot:daily I'm still seeing errors from svccfg before and after the zfs send. This isn't affecting any of the default instances, since they don't use backup-save-cmd. $ svcprop -p start/user zfs/auto-snapshot:rpool-backup zfssnap $ svcprop -p stop/user zfs/auto-snapshot:rpool-backup zfssnap /etc/user_attr contains: zfssnap::::type=role;auths=solaris.smf.manage.zfs-auto-snapshot;profiles=ZFS File System Management The instance runs as zfssnap and the user *should* be able to change values in smf, right? -B -- Brandon High : bh...@freaks.com _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
