in reply to fork issue

It seems you're working in a mod_perl environment. There exit is replaced by Modperl::Util::exit, which in turns throws an exception, which the modperl controller is supposed to catch, and terminate your request.

If you have an exception handler somewhere in your code, maybe it catches this exception from the emulated exit?

Replies are listed 'Best First'.
Re^2: fork issue
by AlfaProject (Beadle) on Jan 08, 2012 at 10:14 UTC
    From what i know , it always shows me that error when the 'exit' functions is called.
    Maybe because of CGI::Carp(fatalsToBrowser);
    I don't want it interact with the user's browser , but only send email
    He should keep working with the parent ,
    How I do that ?
    Thanks