Bug#528497: asterisk: false EX-CANARY message on startup

[Tzafrir Cohen]

On Fri, May 15, 2009 at 04:02:21PM +0200, Kilian Krause wrote:
> Tzafrir,
> 
> On Wed, May 13, 2009 at 01:02:12PM +0300, Tzafrir Cohen wrote:
> > When Asterisk runs in real-time scheduling priority (-p, the default in
> > Debian), it may not be so nice if it gets into a 100% CPU loop. Thus as
> > of Asterisk 1.6.0 there is a separate Asterisk Canary" child process
> > that runs at a normal priorty and writes every 5 seconds to 
> > 
> >   /var/run/asterisk/alt.asterisk.canary.tweet.tweet.tweet
> 
> ...sounds to me like we would need to initialize that file in the init
> script to make sure the tweet is there when asterisk is launched. Is that a
> possible solution?

I've added a patch from upstream that fixes the problem by running the
canary process after daemonizing. This also means that the canary runs
as the Asterisk user. The problem was that the fork caused the
monitoring thread in the Asterisk process to wake up too soon.

However I still suspect that sudden changes of the system clock may have
a strange effect on the canary mechanism.

-- 
               Tzafrir Cohen
icq#16849755              jabber:tzafrir.cohen at xorcom.com
+972-50-7952406           mailto:tzafrir.cohen at xorcom.com
http://www.xorcom.com  iax:guest at local.xorcom.com/tzafrir