Differences in pthread behaviour glibc/uClibc
vadim at mbdsys.com
Tue May 30 17:20:24 UTC 2006
Ralf Ertzinger wrote:
>On Tue, 30 May 2006 16:11:21 +0200, Ralf Ertzinger wrote:
>>>Ralf could you try to replace execve(...) by if (!vfork())
>>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...
>uClibc mailing list
>uClibc at uclibc.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the uClibc