Most likely, IRC in itself is a line based protocol and hence you need to append a newline to your string. Possibly you are Suffering From Buffering, and appending the newline would also help this. Also consider using one of the IRC modules for parsing and possibly even wrapping all your communications with the IRC server.

Whoops, I updated my original post from

print $sock "PRIVMSG $channel :Thread Finished";
[download]

to

print $sock "PRIVMSG $channel :Thread Finished\r\n";
[download]

i don't think that's the problem.

$client->send("\r\n");
while (1) {
  my $msg;
   if($client->connected){
        $client->recv( $msg, 1024 );
       print "$msg\n"
    } 
# do closing up here, a webserver won't keep an open socket for you
# each connection is new
}
[download]

It's an IRC server not a web server. The thread function is not doing any recving.

t's an IRC server not a web server.

In your original node you identified the problem as: One of the functions connects to a web page and parses the content

So it dosn't matter if you are an IRC bot, it is still trying to access a web server thru a socket, so you need to deal with the http protocols. This is the most basic ....notice you need to send a Get, or at least a "\n\n", before the web server will respond.

#!/usr/bin/perl -w

# Usage: this_script  192.168.0.1  /~zentara/index.html

use IO::Socket;
unless (@ARGV > 1) { die "usage: $0 host document ..." }
$host = shift(@ARGV);
foreach $document ( @ARGV ) {
    $remote = IO::Socket::INET->new( Proto => "tcp",
    PeerAddr => $host,
    PeerPort => "http(80)",
);
unless ($remote) { die "cannot connect to http daemon on $host" }

$remote->autoflush(1);

print $remote "GET $document HTTP/1.0\n\n";

while ( <$remote> ) { print }
close $remote;
}
[download]

---

I'm not really a human, but I play one on earth Remember How Lucky You Are

Did you test the code out of a thread first?

Because if it doesn't run properly in-line, it won't run properly once you put it into a thread.

It worked fine not in a thread.