keeping perl code from aborting.

[cookspyder]

I have a simple socket client code that sends the contents of a syslog over to a server when it finds an error. It has been working fine in a while loop of read open socket send line and close socket. However I have been having network issues and have found the code is aborting whenever the network has issues. Is there a way to keep the code from aborting? here is the snippet that seems to cause the code to abort.

use File::Tail;
use IO::Socket; 
{
local $/ = "\n";
my $name = 'filename';
$file=File::Tail->new(name=> $name, maxinterval=>3, reset_tail=>0);
while (defined($line=$file->read)) {
# init host and port 
my $host = 'ip_address'; 
my $port = 8265; 
 
 
 
 
my $sock = new IO::Socket::INET( PeerAddr => $host, PeerPort => $port, Proto => 'tcp'); 
$sock or die "no socket: $@"; 
 
chomp $ln;
print $sock $line;
 print "$line";
 close $sock;
}
}
 

Thanks!!

[numberwhun]

I have a simple socket client code that sends the contents of a syslog over to a server when it finds an error. It has been working fine in a while loop of read open socket send line and close socket. However I have been having network issues and have found the code is aborting whenever the network has issues. Is there a way to keep the code from aborting? here is the snippet that seems to cause the code to abort.

use File::Tail;
use IO::Socket; 
{
local $/ = "\n";
my $name = 'filename';
$file=File::Tail->new(name=> $name, maxinterval=>3, reset_tail=>0);
while (defined($line=$file->read)) {
# init host and port 
my $host = 'ip_address'; 
my $port = 8265; 
 
 
 
 
my $sock = new IO::Socket::INET( PeerAddr => $host, PeerPort => $port, Proto => 'tcp'); 
$sock or die "no socket: $@"; 
 
chomp $ln;
print $sock $line;
 print "$line";
 close $sock;
}
}
 

Thanks!!

I am not sure about the aborting issues, as I don't have any experience with sockets, but you should really have the pragmas "use strict" and "use warnings" in all of your code. A number of the people here require it in your code as it cuts down on the typical errors that can be readily fixed, yet cause false issues compared to the real issue(s) at hand.

Regards,

Jeff

[KevinADC]

Maybe you can change the maxinterval value?

maxinterval=>3