HP3000-L Archives

June 2005, Week 4

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
John Clogg <[log in to unmask]>
Reply To:
John Clogg <[log in to unmask]>
Date:
Thu, 23 Jun 2005 14:23:20 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (40 lines)
-----Original Message-----
From: HP-3000 Systems Discussion [mailto:[log in to unmask]] On
Behalf Of Kim Borgman
Sent: Thursday, June 23, 2005 9:38 AM
To: [log in to unmask]
Subject: RUN AWAY JOB

Had a job last nite with displays run away and cause system to lock,
causing
us to do a restart.  Like 800,000,000 lines.

Is there a way to limit a job to a set number of CPU seconds to prevent
this
?

Or any other slick ideas ?

Donna wrote:
> you might want to consider monitoring your cpu usage...  
> ...this has saved me more than once because a run-away 
> job is likely to consume the entire box.

Well, that might be true for a single-processor system, but since most
jobs in an MPE environment would be running only a single process at any
given time, it would only "use up" one of the processors on a
multiprocessing system.  

As for the question about how big to make your OUT.HPSPOOL file limit,
make it VERY BIG.  As Donna implied, the goal isn't to limit the size of
reports, it's to prevent the system from hanging in the event something
gobbles up all your disk space.  If your system is still up and
responding, you can manually abort jobs, purge files, etc.

John Clogg

P.S., Remind me to avoid the Albuquerque bus station.

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

ATOM RSS1 RSS2