And about the signals: it's _not_ a Python problem. Sometimes Python
doesn't get the signal, but the main problem is killing child apps. If
Python starts a child, it's gets the id. If this child is using
threads, 'kill' on the uid may not kill everything. But you can use
the killall function in util to kill e.g. all mencoder with foo.avi in
the parameter list.
Python is blocking almost all of the signals to child processes (which are started inside threads for Freevo?). The (or one of the) only signal that will get through is KILL (-9). This is _very_ bad! So we have os.system('kill -9 ..') stuff all over the place. These child processes will not clean up after themselves. If someone's mencoder process is saving an avi file and we stop it, it won't get indexed... that's just one example. Also if someone is using the runtime, and their libc is different, it is possible that and os.system() calls will fail unless they include something like the old runapp command that will use the runtime's preloaded libraries.
I really think we should solve this signal blocking issue. I have started reading some docs on python's signalling and threading.
-Rob
------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php _______________________________________________ Freevo-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freevo-devel
