Because the inner process could theoretically die, and you don't want the outer process to die too, and/or you don't want to worry about spill-over from one instance of the inner process to the next (even if it's just memory usage). I have one client that does long, complicated data imports, and I use a master script to call scripts that process individual data sets. So it's not necessarily a bad approach.
in reply to Re: Perl Command Prompt while executing perl script through cgi
in thread Perl Command Prompt while executing perl script through cgi