I would write it like this. Basically, the change that I made is to have it so that the parent continues to fork off children to do its bidding, while the child downloads then exits. You were very close: 
#!/usr/bin/perl -w

use LWP::Simple;
use strict;
my @urls = qw!http://www.cnn.com/
http://www.bbc.com/
http://www.news.com/!;


for my $url (@urls) {
    get_em($url);
}

sub get_em { 
    my $url = shift;
    unless (my $pid = fork) {
        die "Couldn't fork on $url" unless defined $pid;
        die "Malformed url $url" unless $url =~ m!http://www.(.*?)/!;
              
        my $response = getstore($url, "$1.txt");
        die "$url get failed" if is_error($response);
        exit;
    }
}

[download]
Update: Moved the malformed url check
Update: See tilly's reply



Code is (almost) always untested.
http://www.justicepoetic.net/

In reply to Re: fork subroutine by jweed
in thread fork subroutine by aquitaine

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.