Perl on CentOS running at wrong priority level?

[artimus]

I saw a few posts here from Matt Florell in regards to running vici on CentOS.

http://www.eflo.net/VICIDIALforum/viewtopic.php?p=10610
http://www.eflo.net/VICIDIALforum/viewtopic.php?p=3679

The verdict was that perl scripts were running a lower priority level, and thus not running as needed. I am wondering how this was determined? Perl appears to be running at priority 0.

Perhaps someone working with vici/dialtrixbox may know?

As a test I edited limits.conf to make anything run by root run at -10 priority. I can see that this is working, however vici still hangs up on everyone.

[gardo]

I haven't found or encountered the issues posted on those link. The perl scripts always run w/ 0 priority just like any other programs ran by root. I've been using CentOS 64bit for quite some time now and not once did I encounter those issues.

[peacy]

Same here. I have been using CentOS 5 x86_64 and haven't seen any of those problems.

[mflorell]

It seems some pre-built CentOS distros have kernel process preemption set to something other than "server(no preemption)". This causes all sorts of problems for VICIDIAL, and I have not seena reliable way of checking for this other than to run make menuconfig if there is a kernel .config file in /usr/src/linux

[peacy]

If a kernel was installed from an rpm, then the config file is usually included in /boot.
For CentOS5.0 both of the pre-built kernels I've been using (2.6.18-8.el5 & 2.6.18-8.1.8.el5) have "# CONFIG_PREEMPT is not set".