| To: | Ken McDonell <kenj@xxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: Derived metric issues |
| From: | "Frank Ch. Eigler" <fche@xxxxxxxxxx> |
| Date: | Sun, 21 Feb 2016 08:08:18 -0500 |
| Cc: | "'Lukas Berk'" <lberk@xxxxxxxxxx>, pcp@xxxxxxxxxxx |
| Delivered-to: | pcp@xxxxxxxxxxx |
| In-reply-to: | <000101d16c5b$0feb2ef0$2fc18cd0$@internode.on.net> |
| References: | <56B99888.2020408@xxxxxxxxxx> <56BA4445.2030404@xxxxxxxxxxxxxxxx> <8737ssptwp.fsf@xxxxxxxxxx> <y0m7fi4bo0d.fsf@xxxxxxxx> <000101d16c5b$0feb2ef0$2fc18cd0$@internode.on.net> |
| User-agent: | Mutt/1.4.2.2i |
Hi, Ken - > [...] > And finally the man page now reads like this ... > [...] Catastrophic errors such as not being able to open one of the > files on the given path will cause an immediate return with a > negative return value [...] Is it obvious that such an error must be considered "catastrophic"? The string parameter is now a colon-separated path with directories and/or files. Why would we want to stop after the first "not being able to open", instead of continuing? - FChE |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | pcp updates: pmLoadDerivedConfig() changes, Ken McDonell |
|---|---|
| Next by Date: | RE: Derived metric issues, Ken McDonell |
| Previous by Thread: | RE: Derived metric issues, Ken McDonell |
| Next by Thread: | RE: Derived metric issues, Ken McDonell |
| Indexes: | [Date] [Thread] [Top] [All Lists] |