| To: | Ken McDonell <kenj@xxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: [pcp] pcp updates: qa and pmlogger init script change |
| From: | Nathan Scott <nathans@xxxxxxxxxx> |
| Date: | Mon, 16 Nov 2015 21:23:25 -0500 (EST) |
| Cc: | pcp@xxxxxxxxxxx |
| Delivered-to: | pcp@xxxxxxxxxxx |
| In-reply-to: | <564A816B.3080209@xxxxxxxxxxxxxxxx> |
| References: | <564A4EAF.2060106@xxxxxxxxxxxxxxxx> <37781480.14026461.1447721696684.JavaMail.zimbra@xxxxxxxxxx> <564A816B.3080209@xxxxxxxxxxxxxxxx> |
| Reply-to: | Nathan Scott <nathans@xxxxxxxxxx> |
| Thread-index: | dq39rPFiEwADzicFqnmzbqHbHdUwaQ== |
| Thread-topic: | pcp updates: qa and pmlogger init script change |
----- Original Message ----- > On 17/11/15 11:54, Nathan Scott wrote: > > > > The current behaviour (warn but start anyway) is the result of many, > > many people requesting this (rightly or wrongly) so we'll be getting > > a slew of regression reports if this is changed yet again... > > ... > > OK, the requests are broken, the behavior is broken, but I'll revert the > change. Thanks. I tend to agree, FWLIW, but there are "human factors" involved here, and not starting a daemon when we were just told to start a daemon is too much for some. > > ... - what was > > the problem you've come across that led to this change? > > QA failure on Gentoo ... I'll revisit and see if I can smack the QA > test(s) to either notrun or filter out the badness. OK, taa. cheers. -- Nathan |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | pcp updates, Ken McDonell |
|---|---|
| Next by Date: | pcp updates: merges, Nathan Scott |
| Previous by Thread: | Re: [pcp] pcp updates: qa and pmlogger init script change, Ken McDonell |
| Next by Thread: | pcp updates, Ken McDonell |
| Indexes: | [Date] [Thread] [Top] [All Lists] |