× 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.



I forgot about that.  We used Op's Nav monitors for just this purpose. 
Call a CL program when CPU % got above so high.  Worked great!  Only 
problem is that if it bounces so much then there might be enough of a 
delay from the spike until your program gets called that the spike is 
gone.

Rob Berendt
-- 
"They that can give up essential liberty to obtain a little temporary 
safety deserve neither liberty nor safety." 
Benjamin Franklin 




"Glenn Birnbaum" <gbirnba@rei.com>
Sent by: midrange-l-bounces@midrange.com
01/22/2003 03:03 PM
Please respond to Midrange Systems Technical Discussion
 
        To:     "Midrange Systems Technical Discussion" 
<midrange-l@midrange.com>
        cc: 
        Fax to: 
        Subject:        RE: Best Way to Kill Runaway Interactive Jobs?


There are system monitors available via Ops Nav and Management Central
that can monitor CPU usage and then be set to alarm, page, email, call a
program, whatever you like.  Or companies like Bytware (MessengerPlus)
and BMC (Patrol) have products that handle all sorts of operational
issues.  Ops Nav monitors are a cheap solution, they should be able to
detect and react via a program to a runaway (if you're nervous about
killing a job from an automated process, then just hold it).

HTH,
Glenn

-----Original Message-----
From: Ted Barry [mailto:TBARRY@centralsan.dst.ca.us] 
Sent: Wednesday, January 22, 2003 11:26 AM
To: midrange-l@midrange.com
Subject: Re: Best Way to Kill Runaway Interactive Jobs?


We have some users who shutdown their PC's without signing off the 400.

>>> rob@dekko.com 01/22/03 11:17AM >>>
1)  How does one define a runaway job?  Lots of CPU?  Lots of disk?
Never 
ending but neither of the first two?
We had a runaway query that sucked up disk space.  Set a cap on the
group 
profile and that problem will never occur again.  Try to keep them at 80

to 90% full.
After shooting a few people who insisted on *wrap or *prtwrap for all 
joblogs, the occurance of never ending dropped off significantly.
Instead 
of getting upset because their job ended because their log was full,
they 
now try to find out why their log got full.
Lots of CPU?  Better start delving into the work management API's.

Rob Berendt
-- 
"They that can give up essential liberty to obtain a little temporary 
safety deserve neither liberty nor safety." 
Benjamin Franklin 




"Ted Barry" <TBARRY@centralsan.dst.ca.us>
Sent by: midrange-l-bounces@midrange.com 
01/22/2003 01:11 PM
Please respond to Midrange Systems Technical Discussion
 
        To:     <midrange-l@midrange.com>
        cc: 
        Fax to: 
        Subject:        Best Way to Kill Runaway Interactive Jobs?


Does anyone know of a way to setup a server job to monitor and kill 
runaway interactive jobs?  This invariably happens when one is on 
vacation, but never when you're clued to the system.  Why is that?


_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
list
To post a message email: MIDRANGE-L@midrange.com 
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo.cgi/midrange-l 
or email: MIDRANGE-L-request@midrange.com 
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@midrange.com 
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo.cgi/midrange-l 
or email: MIDRANGE-L-request@midrange.com 
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.



_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@midrange.com To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo.cgi/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo.cgi/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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.