Dirk Meyer wrote:
> Dirk Meyer wrote:
>> Lars Eggert wrote:
>>> One thing I've seen mentioned is that forking from the main thread
>>> will not results in children with blocked signals. If this is true
>>> (and I haven't tested it), then we can work around the issue by using
>>> the main thread as a fork proxy: Have all threads talk to the main
>>> thread when they need to fork something, and have the main thread do
>>> the fork and return child information.
>>
>> Cool that works. Any good ideas how to do that? Right now I just send
>> an event ('fork', childapp, comand) and let the main thread start
>> it. It looks like a bad hack but it's much better than using runapp.
>
> One last thing: _if_ we do it that way, I need a function to get the
> information if this is the main thread. It would be stupid to send an
> event and wait for the main thread to fork when it is the main thread
> (stupid as in it won't work).
OK, taken care of. The signal bug is fixed now. I just checked in a
modified version of childapp. It uses the popen wrapper in
util/popen3. This is thread save. It checks the trace if we are a
thread or not. If we are it sends an event to start a child, handled
by main.py. Rob: there is a check if we are the recordserver. I don't
know twisted, you should add some code here to let the twisted main
thread handle processes too, to make sure you can kill the child
later.
Aber killing: since the main thread started the child, the thread
itself has no child to wait for :-(. There is also a waitpid
wrapper. It must be called in the main thread without parameter to do
the real waitpid and the thread can poll if the child is dead.
Aubin: since your child problems started when I removed the runtime,
maybe they are gone now. Please make a fresh checkout, remove the
extra 'quit' in mplayer and xine and test it.
Dischi
--
server4:~# restarting braind....
server4:~# /usr/lib/intelligence not found. core dumped.
-------------------------------------------------------
This SF.net email sponsored by: Enterprise Linux Forum Conference & Expo
The Event For Linux Datacenter Solutions & Strategies in The Enterprise
Linux in the Boardroom; in the Front Office; & in the Server Room
http://www.enterpriselinuxforum.com
_______________________________________________
Freevo-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freevo-devel
