Differences in pthread behaviour glibc/uClibc

[Vadim Lebedev]

Ralf Ertzinger wrote:

>Hi.
>
>On Tue, 30 May 2006 16:11:21 +0200, Ralf Ertzinger wrote:
>
>  
>
>>>Ralf could you try to replace execve(...)  by if (!vfork())
>>>execve(...)?
>>>      
>>>
>>That works, at least under uClibc. I think that may be sufficient
>>as a workaround.
>>    
>>
>
>On the other hand...
>asterisk uses execvp() to restart itself, so the solution above is
>prone to several races for system resources (files, sockets and
>so forth). I admit that this was not visible from my initial post.
>  
>
Usually exec... does not close any files and release any resources...  
so it should not pose problem...
I mean asterisk surely takes care of all this stuff by itself...

Vadim

>_______________________________________________
>uClibc mailing list
>uClibc at uclibc.org
>http://busybox.net/cgi-bin/mailman/listinfo/uclibc
>
>
>
>  
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.busybox.net/pipermail/uclibc/attachments/20060530/57e7fb15/attachment.htm