The command: *zonecfg -z zonename set limitpriv=default,proc_*
*priocntl,sys_time* actually fixed the problem. I thought it didn't but
only to realize I didn't reboot the zone. That was my bad. Thanks so much
for the support.
Kind Regards.
On Thu, Jan 25, 2018 at 11:18 AM, Andy Fiddaman
On Thu, 25 Jan 2018, Software Information wrote:
; I ran
; # zonecfg -z zonename set limitpriv="proc_priocntl"
;
; But it resulted in:
; zonename:* invalid privilege: sys_mount*
You need to add the privilege, not replace what's already there:
# zonecfg -z zonename set
On Thu, 25 Jan 2018, Software Information wrote:
; Hi. Thanks for replying.
;
; Running zonecfg -z zone_name info | grep limitpriv results in:
; limitpriv: default,dtrace_proc,dtrace_user,
;
; *sys_time*
; So that's still there
Try adding proc_priocntl too. Seems it's also needed by NTP.
Andy
On January 25, 2018 1:51:05 AM UTC, Software Information
wrote:
>Hi All
>Today I made the switch updating my r151020 box to omniosce in
>production
>and I am now left with just two issues.
>
>ntp won't start on one zone. All the dependent services are online.
>
>The
On Wed, 24 Jan 2018, Software Information wrote:
; Hi All
; Today I made the switch updating my r151020 box to omniosce in production
; and I am now left with just two issues.
;
; ntp won't start on one zone. All the dependent services are online.
;
; The log says:
; [ Jan 24 19:04:50 Method
Hi All
Today I made the switch updating my r151020 box to omniosce in production
and I am now left with just two issues.
ntp won't start on one zone. All the dependent services are online.
The log says:
[ Jan 24 19:04:50 Method "start" exited with status 96. ]
[ Jan 24 19:49:39 Enabled. ]
[ Jan