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 die, send signal 15
[15/May/2017:16:38:40][23802.7f2f0d7fa700][-nsproxy:reap-] Error: process
5174 killed with signal 15 (Terminated)
On 15 May 2017 at 14:45, Gustaf Neumann <neum...@wu.ac.at> wrote:
>
> i've made the code more robust .... although it is not clear to me yet,
> how the
> proxy can be "Busy" without having a slave... maybe a race condition. I
> will check.
> -g
>
>
------------------------------------------------------------------------------
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
