| To: | "Frank Ch. Eigler" <fche@xxxxxxxxxx>, Dave Brolley <brolley@xxxxxxxxxx> |
|---|---|
| Subject: | Re: [pcp] PCP Updates: qa fallout from ipv6/unix sockets for pmlogger and pmlc |
| From: | Nathan Scott <nathans@xxxxxxxxxx> |
| Date: | Tue, 18 Feb 2014 15:04:21 -0500 (EST) |
| Cc: | pcp@xxxxxxxxxxx |
| Delivered-to: | pcp@xxxxxxxxxxx |
| In-reply-to: | <y0mmwhoqu69.fsf@xxxxxxxx> |
| References: | <52FE5058.4030702@xxxxxxxxxx> <53023D4E.1060504@xxxxxxxxxx> <y0mmwhoqu69.fsf@xxxxxxxx> |
| Reply-to: | Nathan Scott <nathans@xxxxxxxxxx> |
| Thread-index: | Cp9QjdpQdDKR7wKqIXT55+Hz0ct42g== |
| Thread-topic: | PCP Updates: qa fallout from ipv6/unix sockets for pmlogger and pmlc |
----- Original Message ----- > brolley wrote: > > Handle unix domain socket binding (creation) for pmlogger when run > > as a normal user. When running as a normal user, pmlogger is unable > > to bind to (i.e. create) a unix domain socket in /var/run/pcp > > (PCP_RUN_DIR), because that directory is not writable by normal > > users. [... so skip it ...] > > Another solution would be to bind the socket to another predictable > path that is private to the user. It would be desirable let people > have personal pmloggers that are just as immune to foul play as system > pmloggers will be (once they switch onto authenticated-AF_UNIX-only > pmlc). > A great idea! We could use ~/.pcp/pmlogger (which also houses the pmchart/pmcollectl/pm* personal recordings, so maybe not there) or ~/.pcp/tmp/pmlogger ala ($PCP_TMP_DIR/pmlogger) - somewhere below ~/.pcp anyway. cheers. -- Nathan |
| Previous by Date: | reply, edwin morgan |
|---|---|
| Next by Date: | That pmie tmpdir QA fallout change, Nathan Scott |
| Previous by Thread: | Re: PCP Updates: qa fallout from ipv6/unix sockets for pmlogger and pmlc, Frank Ch. Eigler |
| Next by Thread: | Re: [pcp] PCP Updates: qa fallout from ipv6/unix sockets for pmlogger and pmlc, Nathan Scott |
| Indexes: | [Date] [Thread] [Top] [All Lists] |