pcp
[Top] [All Lists]

Re: [pcp] Few doc issues

To: pcp@xxxxxxxxxxx
Subject: Re: [pcp] Few doc issues
From: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
Date: Mon, 22 Feb 2016 15:09:53 +1100
Cc: Marko Myllynen <myllynen@xxxxxxxxxx>
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <565479F9.2070805@xxxxxxxxxx>
References: <5652E148.1090806@xxxxxxxxxx> <565479F9.2070805@xxxxxxxxxx>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
On 25/11/15 01:53, Marko Myllynen wrote:
> ...
> one more thing that came up is that PCPIntro(1) does not explicitly
> mention when PMCD_REQUEST_TIMEOUT et al should be set. Granted, most
> will rightly assume that they should be set before pmNewContext() but I
> think it'd be nice to spell this out to remove any doubts.

This applies to more than PMCD_REQUEST_TIMEOUT, so rather than clutter the 
description of each environment variable, the following caveat has been added 
near the start of the ENVIRONMENT section

       Note  that  most  uses  of these environment variables are optimized to
       check the environment only the first time the variable might  be  used.
       As the environment usually is not checked again, the only safe strategy
       is to ensure all PCP-related environment variables are set  before  the
       first call into any of the PCP libraries.

<Prev in Thread] Current Thread [Next in Thread>