U are careless:), the ast_set_priority() also call some such functions.<br><br><div><span class="gmail_quote">On 4/6/07, <b class="gmail_sendername">Tilghman Lesher</b> <<a href="mailto:tilghman@mail.jeffandtilghman.com">
tilghman@mail.jeffandtilghman.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">On Friday 06 April 2007, Yuan Qin wrote:
<br>> The ast_log() will lock a mutex if appropriate, but the mutex may be in<br>> locked state already.<br>> Maybe we should use pthread_atfork() instead of fork() or never call some<br>> functions that hold mutex
<br>> before execv() in child process.<br>><br>> Is there something that I missed?<br><br>You missed the fact that the ast_log() only runs if the fork failed, which<br>means it can NEVER happen in the child process, only in the parent (and
<br>only when there is no child).<br><br>--<br>Tilghman<br>_______________________________________________<br>--Bandwidth and Colocation provided by <a href="http://Easynews.com">Easynews.com</a> --<br><br>asterisk-dev mailing list
<br>To UNSUBSCRIBE or update options visit:<br> <a href="http://lists.digium.com/mailman/listinfo/asterisk-dev">http://lists.digium.com/mailman/listinfo/asterisk-dev</a><br></blockquote></div><br><br clear="all"><br>--
<br> Regards