comment on

Ok,fine. Then include the threads module into your code as

use threads;

within the while loop,create new thread for each domain name.

while ($line = $sth->fetchrow_array()) {
#Your code goes here
my $new_thread = threads->new(\&scan_domain, $line);</b>
} 
sub scan_domain {

        my $domain_name = shift;
        print "started thread for $domain_name\n";
        my @list =`nmap $line`;
        
        foreach(@list){      
        if($_=~/open/g){
            $_ =~ s/\/.*//g;
            if($myport)
            {$myport=$myport.','.$_;chomp $myport;} 
            else{$myport=$_; chomp $myport} 
        }
[download]

Even you can return the $myport from the subroutine and update the table outside the subroutine or even you can have that table updating script inside the subroutine, its your wish.

If you want these threads to run as daemon process do not return from the subroutine use infinite loop to process in a frequent time.

Update:

Included threads cpan link

In reply to Re^3: how to write thread which was multithreaded port scan scripts for nmap by vinoth.ree
in thread how to write thread which was multithreaded port scan scripts for nmap by Anonymous Monk

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Think about Loose Coupling
	PerlMonks