Prev: Details about how process scheduler works?
Next: clients, was Re: Details about how process scheduler works?
From: john on 15 Apr 2010 05:32
> check now if SUSv1 supports queued signals at all), eg. SIGUSR1. I
> assume your consumer is already written to process all outstanding
> events when a single notification (of some kind) is delivered, because
> you seem to have supposed from the start that pending notifications
> coalesce.

and therein lies my problem......I hadn't consumed all the notifications
when I had received one doh! I have now put in a while(semop.... with
the sembuf structure having the IPC_NOWAIT flag set and nothing in the
while loop so that it is uber fast. The result being I no longer have
the problem :)

Thanks for your help.

John.
First  |  Prev  | 
Pages: 1 2
Prev: Details about how process scheduler works?
Next: clients, was Re: Details about how process scheduler works?