in reply to Extremely odd behavior with net::ping and fork

Worse yet, after a period of several minutes the pings started coming more frequently that once per minute.

If ip-address.txt contains more than one host/address, there's no pause between them because there's no sleep() in the foreach $host (@ip) loop. There's only a pause after the whole list has been processed.

My Win2K laptop quit responding to commands, and I had to yank the battery to reboot. Attached are the code and the log file that shows the misbehavior.

You can usually force computers to shut down by holding the power button for 4-6 seconds. It's probably a friendlier option than removing the battery.

That's all I have time for right now. I hope it helps.

Replies are listed 'Best First'.
Re^2: Extremely odd behavior with net::ping and fork
by wolfger (Deacon) on Aug 18, 2004 at 13:31 UTC
    If ip-address.txt contains more than one host/address, there's no pause between them because there's no sleep() in the foreach $host (@ip) loop. There's only a pause after the whole list has been processed.
    I realize that. The .txt file contains 4 addresses, but 3 of them are commented out, and should not be pinged (on the "unless" command). Also, you can see the IP being pinged is always the same.

    --
    Believe nothing, no matter where you read it, or who said it - even if I have said it - unless it agrees with your own reason and your own common sense.
    (Buddha)