| To: | "'Frank Ch. Eigler'" <fche@xxxxxxxxxx> |
|---|---|
| Subject: | RE: signal pmlogger |
| From: | "Ken McDonell" <kenj@xxxxxxxxxxxxxxxx> |
| Date: | Sat, 12 Apr 2014 10:35:44 +1000 |
| Cc: | "'Martins Innus'" <minnus@xxxxxxxxxxx>, <pcp@xxxxxxxxxxx> |
| Delivered-to: | pcp@xxxxxxxxxxx |
| In-reply-to: | <y0mha5z5t4v.fsf@xxxxxxxx> |
| References: | <53482BC5.6070203@xxxxxxxxxxx> <y0mr453663h.fsf@xxxxxxxx> <01c401cf55c9$d4322fc0$7c968f40$@internode.on.net> <y0mha5z5t4v.fsf@xxxxxxxx> |
| Thread-index: | AQFjOOwECeWAyGg9kCExpCCyzl4RFwLbJ7mVAiOVnP0BW5en4ZuyiQtA |
Frank notes ... > Note that pmie has no native idea about which pmlogger process (amongst > many locally or conceivably on a network) might be appropriate to target a > with a pmlc connection. Correct. I said it was low-level plumbing ... 8^)> But in lots of cases that matter the pmlogger of interest is easily identified, especially when it is known to be the primary pmlogger on a particular host. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: signal pmlogger, Frank Ch. Eigler |
|---|---|
| Next by Date: | pmlogrewrite questions from the developer meeting, Ken McDonell |
| Previous by Thread: | Re: signal pmlogger, Frank Ch. Eigler |
| Next by Thread: | Re: [pcp] signal pmlogger, Martins Innus |
| Indexes: | [Date] [Thread] [Top] [All Lists] |