"Reinstein, Shlomo" wrote:
>
> Hi,
>
> I've used that method to communicate information between the commitinfo and
> the loginfo of the same commit process - that is, using the pid of the "cvs
> commit" process itself, which is the parent of both.
How have you done this? The pid of the "cvs commit" process itself is
NOT the parent of both commitinfo and loginfo. The fork-and-exec
happens (apparently?) *after* the commit actually occurs. This means
that commitinfo and verifymsg are run by the same pid, but loginfo is
not. As the Cederqvist manual says somewhere, the order of the relevant
*info scripts is this:
1. commitinfo
2. verifymsg
(commit happens if (1) and (2) let it happen)
3. loginfo
(1) and (2) are run by the same parent pid; (3) is not.
> Just one point: In case
> you don't work with a CVS server, and people can access the repository from
> various machines, the pid is not enough for distinguishing between commits,
> you need to use both the pid of the commit process and the name of the
> machine.
Yes, of course. {whap} Duh.
Cheers,
Laird
