Quote:
-2 is actually a lower priority, not a higher one; the higher the number, the higher the priority. What priority and scheduler did you modify it to to get it to function, exactly?
Oh i'm such a newbie
I got confused with the niceness concept,which has a reversed logic (higher number <=> higher niceness <=> lower priority)....
About your question:i honestly don't know very well how the original programmer has set the program's priority,but,using the "chrt -p" command i found out it has a SCHED_RR policy with a priority 0.
I have then used the chrt command to set the child process' policy to SCHED_OTHER (which forces me to use a 0 priority).So i guess that what made it work is the fact that i downgraded the child process from real time to normal (but i'm not sure...can you confirm that?)
Besides,i confess i'm beginning to be a tad confused....After reading your reply i read some more internet resources,finding out about static and dynamic priority,and about their ranges...but also finding some contraddictory informations...see for example
www.csd.uwo.ca/courses/CS3305a/Lectures/casestudies.ppt and ATAD #21 - Linux process priority range A Tip A Day [:: ATAD ::] ....One says that static priority ranges from 0 to 99,the other from -20 to 19....
Lastly,what does the PR value i can see in the "top" command output mean?
Thank you so much for you help,i do appreciate it