testpoint code fails to report system error message on failure
This may happen other places too, but here's one instance I came across recently.
This testpoint code can fail to connect to awgtpman using clnt_create
, for any of a variety of reasons. It does report an error and provide some useful information, which is helpful. But a further error message is available from the system by calling clnt_spcreateerror
, and that is not done, obscuring the actual reason for the failure.
Also, when these error messages are printf
ed from within daqd, they seem to get buffered somewhere and do not emerge in the logs until a subsequent connection to daqd is made.