Lukas Berk <lberk@xxxxxxxxxx> writes:
> [...]
>> So the concept of an "error" here is a bit tricky ...
> [...]
> Perhaps it is simply up to the client author to interpret a return value
> of 0 accordingly?
The man page is not really helpful with that "accordingly" though:
The result from pmLoadDerivedConfig will be the number of
derived metrics loaded from files on the given path, else a
value less than zero in the case of an error.
... because that "else" is not an "else" in the exclusive sense. We
can have both errors -and- some derived metrics loaded. So first
thing would be to clarify the language, so that an app author can know
what she can count on.
Perhaps we can say it's a best-effort load attempt, and only result
codes 0...N are to be expected. (Ditch the negative error codes.)
That gives the author no help as to which derived metrics were in fact
loaded, but that's OK. She'll find that out soon enough when trying a
pmLookup* etc.
- FChE
|