Hi Jeroen, >> Had this been discussed before? Does anyone know about best practices? > If it's truly a fork(), then you get essentially two independent > processes with their own indepdendent signal handlers. > If you mean threads, that's another story and signal handling for > threads is currently not supported in Sage. I see the trouble not in the fork itself, but in the handling of the communication between, but that's the case of "system calls" again.
> "signal handling during system calls" is a very general question, it's > hard to give general advice. Within Sage, the sig_on()/sig_off() > mechanism seems to work well, even when system calls are involved. I'll have a look at the implementation. Regards, Alexander -- Dr. rer. nat. Dipl.-Math. Alexander Dreyer Abteilung "Systemanalyse, Prognose und Regelung" Fraunhofer Institut für Techno- und Wirtschaftsmathematik (ITWM) Fraunhofer-Platz 1 67663 Kaiserslautern Telefon +49 (0) 631-31600-4318 Fax +49 (0) 631-31600-5318 E-Mail alexander.dre...@itwm.fraunhofer.de Internet http://www.itwm.fraunhofer.de/sys/dreyer.html -- -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
