At 11:01 AM -0400 8/15/02, Leonard S. Berkowitz wrote:

>Does anyone have a method to monitor the rising EOF of the Omnidex files
>(file code of -411) so that preventative action can be taken before these
>files fill up?
>
>We hit the fan last night on one of these files. Until the horse was stolen
>from the barn, under the apparent misbelief that these files were
>self-adjusting, we were not monitoring these files. Now we have to start,
>and I'd prefer not to reinvent the axle.

Great mixing :-)

Adager can certainly issue a warning.  I have been accused of being
a bit verbose, so I would like to ask for your help in specifying
the message (WHERE you would like it and WHAT it should say).  My
feeling is that Adager should ALWAYS check up-front.  I never
thought about this, so thanks for the pointer, Leonard.

I'll be out all day at Moscone, so please don't panic if you don't
see an immediate response.  Did I actually write "panic"?  I once
saw a comment (in the source code for some kernel or another) that
stated:  /*  this compiles but panics  */

   _______________
  |               |
  |               |
  |            r  |  Alfredo                     [log in to unmask]
  |          e    |                           http://www.adager.com
  |        g      |  F. Alfredo Rego
  |      a        |  Manager, R & D Labs
  |    d          |  Adager Corporation
  |  A            |  Sun Valley, Idaho 83353-3000            U.S.A.
  |               |
  |_______________|

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *