| To: | Ken McDonell <kenj@xxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: [pcp] pcp updates - pmlc <---> pmlogger access controls |
| From: | Nathan Scott <nathans@xxxxxxxxxx> |
| Date: | Mon, 5 May 2014 03:33:28 -0400 (EDT) |
| Cc: | pcp@xxxxxxxxxxx |
| Delivered-to: | pcp@xxxxxxxxxxx |
| In-reply-to: | <536717E1.7080002@xxxxxxxxxxxxxxxx> |
| References: | <536717E1.7080002@xxxxxxxxxxxxxxxx> |
| Reply-to: | Nathan Scott <nathans@xxxxxxxxxx> |
| Thread-index: | BAIY9qlYr8h/4GgHZ5Eh8giR13N0wQ== |
| Thread-topic: | pcp updates - pmlc <---> pmlogger access controls |
Hi Ken, ----- Original Message ----- > Another item from the last developers conf call. > [...] Awesome. :) I'm seeing a QA failure on 381 - looks like the pmlc flush command is able to get EPERM under some conditions. Could be a primary logger using the (pre-existing) system logger config with a new pmlc? Since flush is now a no-op, should this just always succeed perhaps, independent of any permission settings? .bad file attached - everything else is passing for me here. cheers. -- Nathan
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | pcp updates: pmgetopt, Nathan Scott |
|---|---|
| Next by Date: | Re: [pcp] sosreport and pcp, Ken McDonell |
| Previous by Thread: | pcp updates - pmlc <---> pmlogger access controls, Ken McDonell |
| Next by Thread: | RE: [pcp] pcp updates - pmlc <---> pmlogger access controls, Ken McDonell |
| Indexes: | [Date] [Thread] [Top] [All Lists] |