in reply to Ping log terminates unexpectedly

I'm pretty sure Windows 2000 has a 'cron'-type of facility (scheduled task, or whatever it is called), to have the OS call your script periodically. With a little modification you could have your script do the probing and terminate within 60 seconds, and have the OS startup an new script every 60 seconds.

From your last description it sounds like you run your stuff from a terminal window. It should also be possible to run it as a service/in the background so it is not dependant on somebody/something terminating your terminal window. This doesn't exclude something/somebody terminating your script itself ofcourse.

Also, for network performance/failure type of measurements there are some excellent pieces of software available (written in perl):

Replies are listed 'Best First'.
Re^2: Ping log terminates unexpectedly
by nimdokk (Vicar) on Mar 23, 2006 at 15:47 UTC
    Windows 2000 has an 'at' utility as well as a Scheduled Task feature. I'm not sure if the scheduled tasks can be as fine as every 5 seconds though. In my opinion, pinging every 5 seconds might be a bit excessive (and depending on your environment, might set off intrusion alarms). Perhaps sending a ping every couple of minutes might be a bit easier. Just a thought :-)
[reply]

      The Scheduled Task feature only allows a process to be run every one minute. I can't tell for sure but the at command looks to be the same. I will agree with the above comments that pinging every 5 seconds could degrade network performance if the server is critial enoungh to need to be checked so often.

      Thank you,
      Greg W
      Update: changed some spelling.
[reply]

In Section Seekers of Perl Wisdom