| To: | Nathan Scott <nathans@xxxxxxxxxx> |
|---|---|
| Subject: | Re: [pcp] Fetching proc data from a remote host |
| From: | Chandana De Silva <chandana@xxxxxxxxxxxxx> |
| Date: | Tue, 06 Jan 2015 08:01:56 +1100 |
| Cc: | Ken McDonell <kenj@xxxxxxxxxxxxxxxx>, Mark Goodwin <mgoodwin@xxxxxxxxxx>, pcp@xxxxxxxxxxx |
| Delivered-to: | pcp@xxxxxxxxxxx |
| In-reply-to: | <146712636.3083063.1420435731021.JavaMail.zimbra@xxxxxxxxxx> |
| Organization: | Chandana De Silva |
| References: | <1419894543.5699.4.camel@xxxxxxxxxxxxx> <54A1F9FC.2060302@xxxxxxxxxx> <54A21BB6.5070609@xxxxxxxxxxxxxxxx> <146712636.3083063.1420435731021.JavaMail.zimbra@xxxxxxxxxx> |
| Reply-to: | chandana@xxxxxxxxxxxxx |
Hello Nathan, Thanks for the info. We will be upgrading to 3.10.1 all round, to resolve the memory leak. On Mon, 2015-01-05 at 00:28 -0500, Nathan Scott wrote: > Hi guys, > > Chandana, re possible memleaks affecting that older pmcd, a few fixes over > the last year or so spring to mind as probably related ... > d1bfabb2 Resolve a pmdalinux memory leak in cpu:node resolution > f08713f6 plug memory leak in /proc/interrupts parsing > b1e94cd4 correct stack blowage during ioctl() for network interface > > There are no known pmcd/DSO leaks in more recent pcp versions. Also, one > final option up your sleeve re proc metrics is the pmdaproc(1) -A option. > > cheers. > > -- > Nathan |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Presenting at FOSDEM and DevConf.cz, Lukas Berk |
|---|---|
| Next by Date: | pmchart + Some Archives == Sloooooow, Paul Smith |
| Previous by Thread: | Re: [pcp] Fetching proc data from a remote host, Nathan Scott |
| Next by Thread: | Re: [pcp] pcp updates: pmdaroot, pmdapapi, Mark Goodwin |
| Indexes: | [Date] [Thread] [Top] [All Lists] |