Subject: | |
From: | |
Reply To: | Vance, Jeff H (Cupertino) |
Date: | Thu, 29 Jul 2004 10:17:00 -0700 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
...
> However, speaking from actual experience, when an account
> with a disc space limit reaches that limit, jobs and sessions
> will abort as the file system attempts to allocate new
> extents with "out of disc space" errors. If the LIMIT is cpu
> seconds or connect minutes, the limits are checked when a
> session or job logs on; no jobs or sessions will be aborted
> if the limits are reached during their execution and they
> will proceed to normal EOJ or EOS respectively.
In the summer of '87 we added code to JOB/SESSION to respond when the
virtual space manager (VSM) indicates we're running low on free (and
transient) disk space. In this condition we set the session and job
limits to 0 and display a message to that effect on the console. The
CI's JINFO function allows one to see if the system is in this "degraded
mode", e.g.
:calc jinfo("0", "DegradeMode")
HTH,
Jeff Vance, vCSY
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|
|
|