> BUT, I am seeing messages like:
>
> dlmgmtd[100020]: [ID 498274 daemon.warning] dlmgmt_post_sysevent(3) failed:
> Permission denied
>
I see this dlmgmtd warning in my debug logs. This is generated during
boot time. I think Alan's recent "fix libsysevent to use auths so that
setuid(0) hacks can be removed from nwamd" introduced this, but I'm not
familiar with the sysevents area.
Alan, could you please take a look into this?
> I didn't see this before updating to the latest build.
>
> And when I type
>
> $ nwamadm enable Automatic
>
> I get the message:
>
> nwamadm: Could not enable ncp 'Automatic': argument is invalid
>
> And also:
>
> $ nwamadm interact
> could not bind to receive events: Insufficient privileges for action
>
> and as root:
>
> # nwamadm interact
> could not bind to receive events: entity not found
>
> So it looks like I'm having some sort of permission issues...
>
Took me a while to figure this out. When nwam is not enabled, nwamadm
gives (used to give) the above errors. I've actually fixed this by
generating more user-friendly error messages.
bash-3.2# svcs nwam
STATE STIME FMRI
disabled 13:59:44 svc:/network/physical:nwam
bash-3.2# nwamadm list
nwamadm: enable 'svc:/network/physical:nwam' to use 'nwamadm'
bash-3.2# nwamadm interact
nwamadm: enable 'svc:/network/physical:nwam' to use 'nwamadm'
bash-3.2# nwamadm enable -t loc myloc
nwamadm: enable 'svc:/network/physical:nwam' to use 'nwamadm'
Anurag
