Thanks.
This does indeed seem to fix the test case I sent - however I'm now getting
a segmentation fault during the "make test".
It's during the second ns_proxy 5.10 test (there are two 5.10s) - "test
ns_proxy-5.10 {check killing active proxy}".
ns_close is being called on an invalid SlavePtr du
Am 15.05.17 um 15:15 schrieb David Osborne:
> Thanks.
>
> This does indeed seem to fix the test case I sent -
good
> however I'm now getting a segmentation fault during the "make test".
bad
i've made the code more robust although it is not clear to me yet,
how the
proxy can be "Busy" without
Thanks - that stops the seg fault... it does seem to leave a lot of zombies
though. This is the output during the ns_proxy test:
[15/May/2017:15:03:47][7028.75c3b700][-command-] Notice: releasing busy
proxy testpool-8
[15/May/2017:15:03:48][7028.7fffc67fc700][-nsproxy:reap-] Warning:
[testpool
In some cases (but not all), Ns_WaitProcess is logging an error
immediately after the reaper sends a signal 15.
It's under these circumstances ReleaseProxy seems to find the proxy Busy
without a slave.
[15/May/2017:16:38:39][23802.7f2f0d7fa700][-nsproxy:reap-] Warning:
[testpool]: pid 5174 won't
Am 15.05.17 um 17:54 schrieb David Osborne:
> In some cases (but not all), Ns_WaitProcess is logging an error
> immediately after the reaper sends a signal 15.
>
> It's under these circumstances ReleaseProxy seems to find the proxy
> Busy without a slave.
>
> [15/May/2017:16:38:39][23802.7f2f0d7
