in reply to print $socket $message

I presume you're talking about IO::Socket::INET?

I've found that the Timeout parameter, when set in the new() method, has no effect if the remote device is not responding.. in which case an alarm() within an eval { } does actually help.

As for attempting to send to a down-host, I have little experience with this, other than using IO::Select and syswrite() to make sending non-blocking, and implementing application-level timeouts to protect against a host going down in the middle of a process.

Replies are listed 'Best First'.
Re^2: print $socket $message
by serg_remote (Initiate) on Nov 23, 2005 at 17:24 UTC
    yep, IO::Socket::INET or sockets made by builtin functions- they're the same.
    you're right, you need to use eval/alarm block anyway but if you use print instead of send it doesn't work.
    and I found no points in manuals about it. I don't know is it a bug or just undocumented feature- in both cases newbies might have stupid problems :(