Hi David, i've committed a version to bitbucket, that should address the problem. Here is what's seems to happen: a) in your example, you are sending exec commands with huge output and a eval-timeout of 1ms b) NaviServer stops it side the eval more or less immediately (after one ms) c) the slave still tries to send the data, but runs into a blocking write operation d) the slave does react in this state by "normal" interactions, causing the hang.
After my change, NaviServer closes in ReleaseProxy() its end manually, in case the slave is busy. -g PS: it is clear, that we do not see in our production environment this problem, since we are not using an eval timeout. ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ naviserver-devel mailing list naviserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/naviserver-devel
