Gaspar, Carson schrieb:
> Mahesh Kunjal wrote:
>
>> This was not enough and the child process started to wait for memory
>>
> to be freed so that the pipe data retrieved can be put in buffer.
>
>> While this child process waited for memory to be freed, the command
>>
> worker thread got woken up and realized that there is data in pipe and
> forked another child. This got repeated and eventually server went out
> of memory.
>
> This is a bug. A second reader should not be created if a prior reader
> still exists. Locking is required here.
>
This is a large bug concerning all mayor installations of nagios.
We've located this bug too and are now working on a solution. We like to
solve this problem, by spawning a thread doing the job of the problem
causing processes. I hope a working patch will be available soon.
Best regards
Percy Jahn
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]