|
On Thu, Jan 11, 2007 at 04:20:35PM +0000, Graeme Fowler wrote:
> On 11/01/2007 16:01, abang wrote:
> >For the sake of completeness, I found the solution myself.
>
> <snip>
>
> Thanks for letting us all know. I think the silence was punctuated by
> a lot of post-Christmas head scratching... there's a lot of people
> with a lot of LVS system out there, and it would seem nobody had seen
> the behaviour you did.
>
> For completeness (and in Joe's absence) :-) can you say which version
> of ldirectord you were running?
>
> Horms, you might want to take a look at it when we know - it might be
> something in LVS triggered by something ldirectord did (was told to
> do). If we don't find it there, then it'll be over to linux-ha.
Sure. Memory leaks with ldirectord's https check have been a long
standing problem. My latest solution to this was to put the https
check in a separate, short-lived, process, which should mittigate
the problem.
So if you are running a version that is more than 6 month old,
then please try a new one. If you are using the new one, or the
leak is not related to https, then it is a new problem :(
On a not very related note: Please CC me on emails you want to bring to
my attention, its easier for me to find them that way :)
--
Horms
H: http://www.vergenet.net/~horms/
W: http://www.valinux.co.jp/en/
|
