Jedy Wang wrote: >> But it does have the ability to change the system default - that seems >> wrong. > Hi Darren, > > Yes, it can change the value of an existing property. But to make the > option only affect the system once, a new property > (config/fastreboot_over? I think) has to be created, and gnome-panel > does not have the privilege to create the property.
Terminology is important here gnome-panel is not running with privilege. It is the user that gnome-panel is running as that has the authorisation to change the property. svc:/system/boot-config:default has: general/action_authorization astring solaris.system.shutdown general/value_authorization astring solaris.system.shutdown If the user is on /dev/console then they will have that authorisation granted to them via the "Console User" RBAC profile. The fact that a new property has to be created strongly hints to me that there is some architecture problem here. It might be with this case it might be with the fast reboot case. Or it could even be something with SMF. Ticking or unticking the box should be equivalent to running "reboot -f" or "reboot -p". This might be easier to resolve if there was away for init(1M) to pass the reboot intent (fast or prom) of what kind of reboot we want - in addition to having an SMF property for the default. >> Does this work at all if the user doesn't have "Primary Administrator" >> profile assigned and only has "Console User" ? > > I think it works if the user doesn't have "Primary Administrator" > profile assigned and only has "Console User" ? Sherry, is this correct? It will work because of the above. However, I think changing the system wide default is the wrong thing to do. It certainly isn't what I would expect of this behaviour. I expect it to be a one time change if I tick or untick that box. -- Darren J Moffat
