| To: | Mark Goodwin <mgoodwin@xxxxxxxxxx> |
|---|---|
| Subject: | Re: PATCH RFC use environment to signify container name for rc scripts |
| From: | fche@xxxxxxxxxx (Frank Ch. Eigler) |
| Date: | Mon, 16 Mar 2015 14:02:33 -0400 |
| Cc: | Nathan Scott <nscott@xxxxxxxxxx>, pcp@xxxxxxxxxxx |
| Delivered-to: | pcp@xxxxxxxxxxx |
| In-reply-to: | <55067A95.4080705@xxxxxxxxxx> (Mark Goodwin's message of "Mon, 16 Mar 2015 17:39:17 +1100") |
| References: | <55067A95.4080705@xxxxxxxxxx> |
| User-agent: | Gnus/5.1008 (Gnus v5.10.8) Emacs/21.4 (gnu/linux) |
Mark Goodwin <mgoodwin@xxxxxxxxxx> writes: > [...] > Something like $PCP_CONTAINER_NAME might prove very useful in contexts > other than rc scripts too. Thoughts? Some docker configurations send container-identification values like $container and $HOSTNAME automatically. The latter in particular could be a good default --container=XXXX parameter for use by pcp clients running within a container. - FChE |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | PATCH RFC use environment to signify container name for rc scripts, Mark Goodwin |
|---|---|
| Next by Date: | Re: [RFC] Minimizing Installation Size for Reduced PCP Footprint, Frank Ch. Eigler |
| Previous by Thread: | PATCH RFC use environment to signify container name for rc scripts, Mark Goodwin |
| Next by Thread: | Re: PATCH RFC use environment to signify container name for rc scripts, Nathan Scott |
| Indexes: | [Date] [Thread] [Top] [All Lists] |