Why should one use a module to get the PID and the PPID of a process
where there are the $$ variable and the getppid() builtin? (Not
mentioning the equivalent POSIX::getpid() and POSIX::getppid()
functions.)
In fact, this is useful on Linux, with multithreaded programs. Linux'
C library, using the linux thread model, returns different values of
the PID and the PPID from different threads. (Other thread models such
as NPTL don't have the same behaviour). This module forces perl to
call the underlying C functions getpid() and getppid().
WWW: http://search.cpan.org/dist/Linux-Pid/
Remove devel/p5-Linux-Pid. It was a p5-Apache-SizeLimit dep, but now that
the latter has been removed, it's time to remove this port, too. Moreover,
a thourough look revealed that Linux::Pid has actually never been invoked
from Apache::SizeLimit.
Add port devel/p5-Linux-Pid:
Why should one use a module to get the PID and the PPID of a process
where there are the $$ variable and the getppid() builtin? (Not
mentioning the equivalent POSIX::getpid() and POSIX::getppid()
functions.)
In fact, this is useful on Linux, with multithreaded programs. Linux'
C library, using the linux thread model, returns different values of
the PID and the PPID from different threads. (Other thread models such
as NPTL don't have the same behaviour). This module forces perl to
call the underlying C functions getpid() and getppid().
WWW: http://search.cpan.org/dist/Linux-Pid/