Hi Ken,
----- Original Message -----
> > -----Original Message-----
> > [...]
> > Or something else. Any thoughts / preferences?
>
> I'd vote for Install scripts then need a non-zero exit status to be told
> about the pmdarproc.sh trap handler protocol.
*nod* - I think this will be generally simpler in the front-end scripts.
> You could rename $__sts to $status if you wish, I donât really have an
> opinion on this part of it.
OK, will probably do that too then, and document it here...
> Indirectly, this raises the point that there is no really adequate
> documentation for the pmdaproc.sh environment that PMDA Install and Remove
> scripts are assumed to run in ... pmda(3) has some brief references but I'm
> pretty sure this is incomplete. The change for the trap / exit status
> propagation might be a good trigger to flush all of the pmdarproc.sh magic
> shell variables out into a (new?) man page?
In the Programmers Guide there's a fair bit of detail on the topic - e.g. in
"Table 2.1. Variables to Control Behavior of Generic pmdaproc.sh Procedures"
http://www.pcp.io/books/PCP_PG/html-single/#LE55181-PARENT
cheers.
--
Nathan
|