AnyEvent-Fork
view release on metacpan or search on metacpan
The process object becomes unusable on return from this function - any
further method calls result in undefined behaviour.
The function name should be fully qualified, but if it isn't, it will be
looked up in the C<main> package.
If the called function returns, doesn't exist, or any error occurs, the
process exits.
Preparing the process is done in the background - when all commands have
been sent, the callback is invoked with the local communications socket
as argument. At this point you can start using the socket in any way you
like.
If the communication socket isn't used, it should be closed on both sides,
to save on kernel memory.
The socket is non-blocking in the parent, and blocking in the newly
created process. The close-on-exec flag is set in both.
The process object becomes unusable on return from this function -
any further method calls result in undefined behaviour.
The function name should be fully qualified, but if it isn't, it
will be looked up in the "main" package.
If the called function returns, doesn't exist, or any error occurs,
the process exits.
Preparing the process is done in the background - when all commands
have been sent, the callback is invoked with the local
communications socket as argument. At this point you can start using
the socket in any way you like.
If the communication socket isn't used, it should be closed on both
sides, to save on kernel memory.
The socket is non-blocking in the parent, and blocking in the newly
created process. The close-on-exec flag is set in both.
( run in 0.868 second using v1.01-cache-2.11-cpan-d8267643d1d )