[Asterisk-Dev] Bug 3203 "Get RT without runaway risk" revisited

[Herman Webley]

On 08/05/05 10:46:13, Tzafrir Cohen wrote:

> But on a 100%cpu loop the watchdog process may never get a chance
> to run its code as Asterisk takes literally 100% of the CPU. The
> watchdog should have real-time priority as well, right?

It seems it works this way:
The watchdog is not realtime priority, thus it does not get to signal  
the wrapper, the wrapper (which is itself realtime) in turn realizes  
that the asterisk process has run away. Perhaps the the naming of the  
components is not clear.

Regards,
Herman Webley