On Fri, Jun 15, 2012 at 10:44 PM, Tzafrir Cohen <span dir="ltr"><<a href="mailto:tzafrir.cohen@xorcom.com" target="_blank">tzafrir.cohen@xorcom.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="HOEnZb"><div class="h5">On Fri, Jun 15, 2012 at 11:56:32AM -0400, Moises Silva wrote:<br>
> On Fri, Jun 15, 2012 at 10:07 AM, Anton Krall <<a href="mailto:antonkrall@gmail.com">antonkrall@gmail.com</a>> wrote:<br>
><br>
> > timerfd was the solution from digium that would not require a dahdi time<br>
> > source right?<br>
> ><br>
><br>
> There is timerfd and pthread timers. Both have been problematic in the past<br>
> to many users, sometimes due to kernel bugs, sometimes due to Asterisk<br>
> bugs, all in all, they do not seem mature yet.<br>
<br>
</div></div>This is for what version of Asterisk?<br>
<span class="HOEnZb"><font color="#888888"><br></font></span></blockquote><div><br>At least for 1.6 I faced problems myself (cpu spinning or deadlocks), I stopped using them altogether since then, and from the comments mentioned by Jam, Asterisk 1.8.5 also has issues with timerfd.<br>
<br>Moy<br></div></div>