From: Zeljko Vrba (zvrba_at_[hidden])
Date: 2008-03-17 11:34:00
On Mon, Mar 17, 2008 at 04:09:53PM +0100, Hughes, James wrote:
>
> Or put a usleep(0) in the thread to force the timeslice to expire? IIRC.
>
Calling sched_yield() would also probably help, but that's a non-solution to
the OP's non-problem. To the OP: if a particular order of execution is desired,
it has to be explicitly coded with various synchronization primitives.