home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.vms
- Path: sparky!uunet!gatech!concert!samba!usenet
- From: Walt.Armour@launchpad.unc.edu (Walt Armour)
- Subject: Determining if process is runaway ?
- Message-ID: <1993Jan5.195143.7160@samba.oit.unc.edu>
- Summary: How?
- Keywords: process runaway CPU
- Sender: usenet@samba.oit.unc.edu
- Nntp-Posting-Host: lambada.oit.unc.edu
- Organization: UNC Office of Information Technology
- Date: Tue, 5 Jan 1993 19:51:43 GMT
- Lines: 21
-
- I am currently working on a sentry-type program to monitor processes
- on our systems. It monitors processes for idle logout and for runaway
- CPU time. The problem I have is determining whether a process is runaway
- or not. The method I was going to use would compare the ratio of CPU time
- to connect time. This works but is not the best. If a user consumes enough
- CPU to prevent becoming idle it could stay logged in for several days then
- begin running away. In that case my sentry could take several days to
- classify a process as runaway.
-
- Are there better (and quicker) methods that determine if a process is runaway
- withing 5-10 minutes?
-
- Tnx,
- Walt
- KD4QZQ
-
- --
- The opinions expressed are not necessarily those of the University of
- North Carolina at Chapel Hill, the Campus Office for Information
- Technology, or the Experimental Bulletin Board Service.
- internet: laUNChpad.unc.edu or 152.2.22.80
-