| To: | Ken McDonell <kenj@xxxxxxxxxxxxxxxx>, Marko Myllynen <myllynen@xxxxxxxxxx> |
|---|---|
| Subject: | Re: [pcp] pmda persistent indom cache access issues, part 2 |
| From: | Nathan Scott <nathans@xxxxxxxxxx> |
| Date: | Thu, 25 Feb 2016 16:04:00 -0500 (EST) |
| Cc: | pcp developers <pcp@xxxxxxxxxxx> |
| Delivered-to: | pcp@xxxxxxxxxxx |
| In-reply-to: | <56CF5866.20407@xxxxxxxxxxxxxxxx> |
| References: | <56CED581.8020305@xxxxxxxxxx> <56CF5866.20407@xxxxxxxxxxxxxxxx> |
| Reply-to: | Nathan Scott <nathans@xxxxxxxxxx> |
| Thread-index: | 5PhjlzrQJZFCgfDwDWyqL3k8kkwy+w== |
| Thread-topic: | pmda persistent indom cache access issues, part 2 |
Hi guys, ----- Original Message ----- > On 25/02/16 21:20, Marko Myllynen wrote: > > Hi, > > > > On RHEL 7 / PCP 3.10.6 I'm hitting the same issue Ken reported > > in http://oss.sgi.com/archives/pcp/2013-05/msg00005.html. > > This is how we install the indom cache directory ... > > $(INSTALL) -m 775 -o $(PCP_USER) -g $(PCP_GROUP) -d > $(PCP_VAR_DIR)/config/pmda > > so unless the PMDA is running as root or pcp, it is not going to be able to > _create_ the indom files. > > For real PMDAs that need to run as some other uid, there only real option is > to create the indom files > and chown/chmod them in the Install script (that does run as root). > The pmdaoracle Install script does this sort of thing, as an example. cheers. -- Nathan |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [pcp] pmda persistent indom cache access issues, part 2, Ken McDonell |
|---|---|
| Next by Date: | [Bug 1286361] SELinux is preventing pmcd from 'read' accesses on the file pmlogger_daily.pid., bugzilla |
| Previous by Thread: | Re: [pcp] pmda persistent indom cache access issues, part 2, Ken McDonell |
| Next by Thread: | Re: [pcp] pmda persistent indom cache access issues, part 2, Nathan Scott |
| Indexes: | [Date] [Thread] [Top] [All Lists] |