http://qs321.pair.com?node_id=374034


in reply to Test::Cmd and forking

I ran into a similar problem myself in my own test code where I didn't want some END blocks to get executed in the child. There are several possibilities to avoid cleanup code when a forked child exits. I thought of a couple (I bet there's more than two ways to do this though). I'm not really satisfied with either of these though.

  1. Rather than exit or die in the child, exec something innocuous, e.g.:

    exec('/bin/true') or exec('perl','-e','')

  2. Another possibility which I thought of but did not test is to have the child send itself a SIGKILL (or maybe a SIGTERM) would be enough?)

Replies are listed 'Best First'.
Re^2: Test::Cmd and forking
by fergal (Chaplain) on Jul 13, 2004 at 21:45 UTC
    You can use Manip::END to selectively delete END blocks. It was written precisely for your situation where you have a fork and a troublesome END block. 
    $ends = Manip::END->new;
# now remove some END blocks
$ends->remove_class("Test::Cmd"); # only those in Test::Cmd
$ends->remove_isa("Test::Cmd"); # in Test::Cmd and any subclasses
$ends->remove_pat('^Test::Cmd(::.*)?$'); # any END blocks from Test::C
+md and Test::Cmd::Whatever

    [download]
    You can also do other manipulations.
[reply]
[d/l]

In Section Seekers of Perl Wisdom