Hi, Af far as I know this function sets real time process priority for Quorum Server:
http://src.opensolaris.org/source/xref/ohac/ohac/usr/src/cmd/scqsd/scqsd.cc#start_child_and_monitor I think PRIV_PROC_PRIOCNTL privilege would be used in this case. What about that? On Sat, Jun 6, 2009 at 4:53 AM, roush<Ellard.Roush at sun.com> wrote: > Hi, > > The Sun Cluster Membership algorithm seeks to recover > in a short time period. This means that the quorum device > must respond quickly. If the quorum device does not respond > quickly, then the cluster cannot count its quorum vote. > A slowly responding quorum device can result in complete > cluster failure. > > In order to ensure that the Quorum Server can respond > in a timely manner, the Quorum Server runs at a very high > real time priority. Things without privileges cannot run > this high. > > If you run the Quorum Server as an ordinary process, > the Quorum Server will FAIL to respond in a timely > manner on a busy system. Your entire cluster can fail. > > The exact system account does not matter. But the > Quorum Server needs its high priority. > > Regards, > Ellard > > Piotr Jasiukajtis wrote: >> >> Hello, >> >> How about that? >> >> On Sat, Apr 25, 2009 at 9:54 PM, Piotr Jasiukajtis<estseg at gmail.com> >> wrote: >>> >>> Hi, >>> >>> Is there any requirement to run Quorum Server as user root? >>> If no, I propose to add a dedicated system account (for example >>> qsuser) and change SUNWscqsr package to run >>> svc:/system/cluster/quorumserver:default service as non privileged >>> account. >>> >>> -- >>> Piotr Jasiukajtis | estibi | SCA OS0072 >>> http://estseg.blogspot.com >>> >> >> >> > -- Piotr Jasiukajtis | estibi | SCA OS0072 http://estseg.blogspot.com
