Re: [Nagios-devel]
Posted: Thu Dec 21, 2006 9:07 am
Am Donnerstag, 21. Dezember 2006 17:56 schrieb Ethan Galstad:
> Good work on nailing down the problem to the command buffer slots!
> Sounds like this problem might affect a number of users, so I think we
> need to patch Nagios. There are two possible solutions:
>
> 1. Bump up the default buffer slots to something larger. Since Nagios
> only immediately allocates memory for pointers, the additional memory
> overhead is fairly small. Allocated memory =3D (sizeof(char **)) * (# of
> slots).
>
> 2. Moving the slots definitions out to command file variables. This is
> a better solution than having to edit the code and recompile.
Yes, make variables for the bufferslots.
Can you please adapt nagiostat to provide the current and max Buffer Slots ?
J=F6rg=20
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]
> Good work on nailing down the problem to the command buffer slots!
> Sounds like this problem might affect a number of users, so I think we
> need to patch Nagios. There are two possible solutions:
>
> 1. Bump up the default buffer slots to something larger. Since Nagios
> only immediately allocates memory for pointers, the additional memory
> overhead is fairly small. Allocated memory =3D (sizeof(char **)) * (# of
> slots).
>
> 2. Moving the slots definitions out to command file variables. This is
> a better solution than having to edit the code and recompile.
Yes, make variables for the bufferslots.
Can you please adapt nagiostat to provide the current and max Buffer Slots ?
J=F6rg=20
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]