Has anyone else experience issues with RHEL5 and the tcl thread support?
Tcl when built with thread support has issues with applications that fork. On some platforms, it's not even possible to fork from a threaded app. The problem is that when a fork syscall occurs, the threads aren't copied. So several things happen, you end up with 2 processes, but the new forked process only has one thread. So you have a bunch of state that becomes garbage in the new process, because mutexs and others aren't guaranteed to be in any state after a fork. Has anyone else dealt with this? Does RedHat even know that this is a problem in RHEL5? __________________________ John F. Russo Manager, Engineering QLogic Corporation 780 Fifth Avenue, Suite 140 King of Prussia, PA 19406 Direct: 610-233-4866 Main: 610-233-4800 Fax: 610-233-4777 Cell: 610-246-9903 Email: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> www.qlogic.com <http://www.qlogic.com> True success is the undeniable truth that we have proved ourselves. -Joe Luppino-Esposito
<<image001.jpg>>
_______________________________________________ rhelv5-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-list
