Am 25.09.15 um 14:46 schrieb Zoran Vasiljevic: > On 25 Sep 2015, at 14:38, Gustaf Neumann <neum...@wu.ac.at> wrote: > >> which will be fixed in 8.5.19, as well as the bug mentioned below (which can >> cause problems for all kinds of forks, when e.g. nsproxy is not used for >> "exec", >> or for nscgi). > Can it be that somebody in Tcl was "too clever" and > short-sightedly wanted to solve the un-solvable? kind of. the fix was addressing a problem in rivet under Linux, the consequences were not easy to spot from the code but hit all multi-threaded tcl applications, including NaviServer. It also lead to bug-reports from bsd about "massive slowdowns". > So Tcl 8.5.18 is really useless for NS? for production, yes.
The forking/exec/cgi problem can be avoided by avoiding exec and nscgi (probably nsphp). The bug was introduced in Tcl 8.5.15 and Tcl 8.6.1. All later Tcl versions are affected. Jan Nijtmans has back-ported the changes yesterday to the Tcl core-8-5tcl-8-5 branch targeted for the next Tcl 8.5 release. So, if one requires a functionality based on fork, the best approach is to stick to Tcl 8.5.14 for the time being. -g ------------------------------------------------------------------------------ _______________________________________________ naviserver-devel mailing list naviserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/naviserver-devel
