| To: | Ken McDonell <kenj@xxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: [pcp] pcp updates - a few odds and sods |
| From: | Nathan Scott <nathans@xxxxxxxxxx> |
| Date: | Wed, 17 Jul 2013 03:54:58 -0400 (EDT) |
| Cc: | pcp@xxxxxxxxxxx |
| Delivered-to: | pcp@xxxxxxxxxxx |
| In-reply-to: | <51E6496C.6040706@xxxxxxxxxxxxxxxx> |
| References: | <51E52372.9060601@xxxxxxxxxxxxxxxx> <226441832.2376946.1374036267711.JavaMail.root@xxxxxxxxxx> <51E6496C.6040706@xxxxxxxxxxxxxxxx> |
| Reply-to: | Nathan Scott <nathans@xxxxxxxxxx> |
| Thread-index: | 36bQxsQgf9oeRobRK31tbjPNQIIGtg== |
| Thread-topic: | pcp updates - a few odds and sods |
----- Original Message ----- > ... > Group pcp won't help on my system because /var/run/pcp is like this ... > drwxr-xr-x 2 root root 80 Jul 17 17:06 /var/run/pcp > In latest dev it should be installed as root:pcp (for pmcd unix domain socket file). > Since in real environments pmlogger_daily and pmlogger_check are always > (?) going to be run from root's crontab, is the real fix to make QA use > $sudo when running these scripts? If yes, I'll fix it. If no, I'm open > for suggestions. Works for me. BTW, its running from the "pcp" user crontab nowadays (in latest dev), to further reduce out running-as-root-user attack surface area. Seems to work just fine that way from my testing so far. cheers. -- Nathan |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [pcp] pcp updates - a few odds and sods, Ken McDonell |
|---|---|
| Next by Date: | pcp updates: brolley, kenj, qa, Nathan Scott |
| Previous by Thread: | Re: [pcp] pcp updates - a few odds and sods, Ken McDonell |
| Next by Thread: | pmdagfs2: Improved distribution support and QA updates, Paul Evans |
| Indexes: | [Date] [Thread] [Top] [All Lists] |