On Tue, Feb 01, 2005 at 11:03:46AM +0100, Kilian Krause wrote: > Hi CuPoTKa, > > > Setting AST_REALTIME="yes" to "no" helps, but asterisk starts without > > high priority. > > > > There's no problem starting it from command line, even with -p (high > > priority) flag. Problem only with init script. > > yes, that's due to the fact that some other users complained about the > -U and -G not working effectively enough for their needs. The dilemma is > that either we let asterisk drop privileges *AFTER* setting realtime > prio (launching as root and being limited to one group), or we switch to > that asterisk user *BEFORE* launching asterisk (and getting all the > groups, but asterisk user cannot set realtime-prio).
-G/-U and -p can co--exist peacefully . WorksForMe (Xorcom Rapid). Unless in my tests Asterisk silently ignored -p . Anyway, -G and -U do require changing the ownership for some files. Otherwise Asterisk won't start. -- Tzafrir Cohen icq#16849755 +972-50-7952406 [EMAIL PROTECTED] http://xorcom.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
