pcp
[Top] [All Lists]

Re: pmmgr memory hog

To: "Frank Ch. Eigler" <fche@xxxxxxxxxx>
Subject: Re: pmmgr memory hog
From: Nathan Scott <nathans@xxxxxxxxxx>
Date: Thu, 5 Feb 2015 18:04:24 -0500 (EST)
Cc: pcp@xxxxxxxxxxx
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <20150205225822.GA28568@xxxxxxxxxx>
References: <23273355.372.1423022546978.JavaMail.rmckee@wsrmckee> <1838902881.6952157.1423024805273.JavaMail.zimbra@xxxxxxxxxx> <y0md25p63ji.fsf@xxxxxxxx> <1683339037.8571387.1423176489834.JavaMail.zimbra@xxxxxxxxxx> <20150205225822.GA28568@xxxxxxxxxx>
Reply-to: Nathan Scott <nathans@xxxxxxxxxx>
Thread-index: UI247wQjQ0ljx9AMnkqCslyZ3ek2Cg==
Thread-topic: pmmgr memory hog

----- Original Message -----
> > | Have made it go away by stopping it and preventing it from starting.
> 
> OK, that suggests they may be unable / unwilling to help debug
> further.  Nevertheless, please ask the reporter to forward his/her
> /var/log/pcp/pmmgr/pmmgr.log* files.

I asked (yep, with full path), but none were forthcoming / found.

What's our level of confidence re valgrind vs pmmgr? - could make
a good pmmgr QA test.

cheers.

--
Nathan

<Prev in Thread] Current Thread [Next in Thread>