× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Bug w/ Ping command?
  • From: "Leland, David" <dleland@xxxxxxxxxx>
  • Date: Thu, 11 Dec 1997 14:20:00 -0500

Ran across something interesting today.  We were running a never-ending
program which simply did a PING to a few IP addresses every 10 seconds
to keep the addresses alive.  After running for a couple days I noticed
our disk usage had gone up dramatically.  Within two days it went from
41% to 49%.  After looking for the obvious, I thought about that job and
when I looked at it I noticed that it had used so much temporary storage
that it was all '+++++++++++'.  Funny thing is, there was nothing in
it's QTEMP library that was of any size at all.  I did an ENDJOB *IMMED
on it and after about 2 hours it finally ended and our disk usage was
back down to it's normal place.

I'm running the program again and watching it's Temporary storage used,
and everytime it does a PING, it jumps up about 40 and never goes back
down.  So, the question is, is this a bug w/ PING or is there something
I can do to reclaim that Temporary storage after everytime it does a
ping?

Dave
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.