in reply to How aggressively does Perl clean up when you exit()?

If your OS doesn't clean up that type of stuff when a process exits, you probably should get a better OS. The only things I could think wouldn't get cleaned up automagically would be things like shared memory or semaphores, and you could possibly have lingering socket connections in TIME_WAIT states depending on how you set your socket options.

  • Comment on Re: How aggressively does Perl clean up when you exit()?

Replies are listed 'Best First'.
Re: Re: How aggressively does Perl clean up when you exit()?
by Rex(Wrecks) (Curate) on Nov 14, 2001 at 22:15 UTC
    I doubt there will be lingering socket connections since those are treated as FileHandles and all FileHandles should be wiped. Shared memory can be nuked by putting in this catching the INT signal like this:

    $SIG{INT} = sub { IPC::Shareable->clean_up_all ; exit 0;} ;

    You might want to catch other signals as well for this, however this catches everything I have ever run into except a perl core dump.

    Update: Hmmm, crazyinsomniac has said that you can't/shouldn't exit when catching INT. I will take his word on it, as he has been perling longer than I I'm sure. However this has been working for me in an existing implementation, maybey I'm bound for a crash!! I'll have to debug it futher.

    "Nothing is sure but death and taxes" I say combine the two and its death to all taxes!
[reply]
[d/l]
[select]
      Try a different signal or better yet setup an END{} See perlfunc:exit.
[reply]

In Section Seekers of Perl Wisdom