| To: | pcp@xxxxxxxxxxx |
|---|---|
| Subject: | Re: [pcp] Fetching proc data from a remote host |
| From: | Ken McDonell <kenj@xxxxxxxxxxxxxxxx> |
| Date: | Tue, 30 Dec 2014 14:27:50 +1100 |
| Delivered-to: | pcp@xxxxxxxxxxx |
| In-reply-to: | <54A1F9FC.2060302@xxxxxxxxxx> |
| References: | <1419894543.5699.4.camel@xxxxxxxxxxxxx> <54A1F9FC.2060302@xxxxxxxxxx> |
| User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 |
On 30/12/14 12:03, Mark Goodwin wrote: > ... most likely pmdaproc on the remote host is running as the pcp user, which doesn't have access to all of the /proc/<pid>/... data for users other than pcp. The proc.nprocs metric is extracted from /proc/stat, which doesn't have such access restrictions (world readable). And the metrics _will_ be available on the same host as pmcd using -h local: (default for most tools, but not pmchart I just discovered) because the connection uses a local domain socket and the access control rules are relaxed compared to connection to pmcd via an ip socket (like a remote pmlogger uses). |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [pcp] Fetching proc data from a remote host, Chandana De Silva |
|---|---|
| Previous by Thread: | Re: [pcp] Fetching proc data from a remote host, Chandana De Silva |
| Indexes: | [Date] [Thread] [Top] [All Lists] |