Donald Sharp wrote:
> 
> What does it matter?

1. If my commitinfo script leaves a dropping behind it in the cvs temp
directory (which is of the form /tmp/cvs-serv20873 when cvs is invoked
via rsh or pserver or probably gserver), and my loginfo script wants to
retrieve that dropping, the loginfo script needs to know the name of the
temp directory.

2. To get the name of the temp directory, the loginfo script needs to
know the pid of the cvs process that ran commitinfo, because that's
embedded in the temp directory name, as detailed above.

3. But the pid changes between commitinfo time and loginfo time.  So I'm
trying to see if it changes deterministically.

> more than likely cvs is just forking and execing...

Doesn't a fork and exec result in...two addi...aha, but the second cvs
(the one that's exec'ed) is then invoking my loginfo script so that's
why loginfo getppid() returns commitinfo.getppid() + 3.  Got it.

Cheers,
Laird

Reply via email to