| To: | "Frank Ch. Eigler" <fche@xxxxxxxxxx> |
|---|---|
| Subject: | Re: [pcp] pcp updates: qa, containers |
| From: | Nathan Scott <nathans@xxxxxxxxxx> |
| Date: | Wed, 18 Mar 2015 20:30:09 -0400 (EDT) |
| Cc: | Mark Goodwin <mgoodwin@xxxxxxxxxx>, pcp <pcp@xxxxxxxxxxx> |
| Delivered-to: | pcp@xxxxxxxxxxx |
| In-reply-to: | <20150318143821.GA15881@xxxxxxxxxx> |
| References: | <839234551.7808463.1426575003930.JavaMail.zimbra@xxxxxxxxxx> <1452631543.7808485.1426575023285.JavaMail.zimbra@xxxxxxxxxx> <y0m7fufmqxd.fsf@xxxxxxxx> <5508CEA0.3060107@xxxxxxxxxx> <1761824975.8325622.1426651846865.JavaMail.zimbra@xxxxxxxxxx> <20150318143821.GA15881@xxxxxxxxxx> |
| Reply-to: | Nathan Scott <nathans@xxxxxxxxxx> |
| Thread-index: | z82vfP+VrAkmZzVAvloc2lSO0Odd1g== |
| Thread-topic: | pcp updates: qa, containers |
----- Original Message ----- > > > > container pid-1 would actually exit when the daemon does, [...] > > > > Not sure what code you're looking at, but that *is* what happens already. > > [...] could be routed to "pmpause" and cause an early death. It exits on final child exit, or on a termination signal. It has the exact sought-after behaviour here and no more, no less. All notes Mark and I made were shared; from memory, I don't think we kept specific details on all the startup issues though (we were in the zone for several hours and scribed later, so woulda missed *many* details, sorry). cheers. -- Nathan |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [pcp] possible collectd interoperation options, Martins Innus |
|---|---|
| Next by Date: | RE: QA resource leaks, Ken McDonell |
| Previous by Thread: | Re: [pcp] pcp updates: qa, containers, Frank Ch. Eigler |
| Next by Thread: | Valid metric names, Martins Innus |
| Indexes: | [Date] [Thread] [Top] [All Lists] |