On Fri, 2007-09-14 at 15:08 +0100, Michael Bane wrote: > I've just acquired a box with an Intel Core2 Duo. It's running Fedora: > [EMAIL PROTECTED]:~$ uname -a > Linux veri.phy.umist.ac.uk 2.6.22.4-65.fc7 #1 SMP Tue Aug 21 21:50:50 > EDT 2007 x86_64 x86_64 x86_64 GNU/Linux > > and I have set MaxLoad and MinLoad in my prime.ini but these are not > being honoured. Any ideas? > <Michael> > > [EMAIL PROTECTED]:~/mprime$ less prime.ini > OldUserID= > OldUserPWD= > UserPWD=mkb99 > UserName=michael > [EMAIL PROTECTED] > Newsletters=0 > UserID=iceni > AskedAboutMemory=1 > UsePrimenet=1 > DialUp=0 > DaysOfWork=2 > WorkPreference=0 > MaxLoad=1.9 > MinLoad=1.1 > PauseTime=3 > > top - 15:07:47 up 10 days, 4:58, 11 users, load average: 2.18, 2.10, > 2.18 > Tasks: 162 total, 4 running, 158 sleeping, 0 stopped, 0 zombie > Cpu(s): 2.6%us, 0.7%sy, 0.9%ni, 94.7%id, 0.5%wa, 0.1%hi, 0.5%si, > 0.0%st > Mem: 3989488k total, 1331328k used, 2658160k free, 58332k buffers > Swap: 2031608k total, 292344k used, 1739264k free, 502920k cached > > PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ P > COMMAND > > 20657 mkb 39 19 24400 18m 720 R 100 0.5 30:35.13 0 > mprime > > 20658 mkb 39 19 24408 18m 732 R 75 0.5 30:28.15 1 > mprime >
Okay, I'm unsure what's happening but the above, errant, behaviour changed after a while (ie it now *does* suspend running when code exceeds MaxLoad). I'm wondering if perhaps, given the above was immediately after setting it all up, it's an initialisation/testing/burning in issue... M _______________________________________________ Prime mailing list [email protected] http://hogranch.com/mailman/listinfo/prime
