The above is the behavior I would expect, actually..."while (1);" (in a
test compile I just did) generates a two-instruction infinite loop (two
jmp's directed at each other), so a process suck in a while(1); is
indistinguishable from any other very CPU-intensive process.
If you really want a process to idle rather than busy-wait, use something
like sleep() or select() on /dev/null. That way, Linux can put the
process on an idle queue where it won't use any cycles; as long as the
process is _doing_ something (and jumping back and forth between two PC's
is, like it or not, "doing something"), it will continue to get
timeslices.
Adam
-- He feeds on ashes; a deluded mind has led him Adam Bradley, UNCA Senior astray, and he cannot deliver himself or say, Computer Science "Is there not a lie in my right hand?" Isaiah 44:20 bradley@cs.unca.edu http://www.cs.unca.edu/~bradley <><