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.
Dischi
--
"There is no reason for any individual to have a computer in their
home." (Ken Olsen, Pr�sident von DEC, 1977)
-------------------------------------------------------
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
