| Yes, like all idle process deletion utilities SYS$GETJPI is used
to determine information about the user. Since this system call
requires that the user become active to get the information, processes
which are outswapped must be inswapped in order for this to occur.
What this produces is a system which, once a minute, must have all
of its processes active. On a system which normally has a few
processes swapped, the level of swapping will increase.
Currently, one of the additions which has become important to Zap
is that it be able to monitor people by device, thus enabling it
to only affect those users which must be monitored.
Unfortunately, there is no method at this time to monitor people
without SYS$GETJPI.
Any suggestions on a better method would be greatly appreciated.
Keith Maconi
|
|
I remember reading, somewhere, that only *some* GETJPI items require
a process to be swapped in. I don't know which do and which don't.
Note that the SHOW SYSTEM command avoids swapping in processes by saying
"-- swapped out --" in place of said info.
Maybe it is possible for Zap to gain enough information about a process
to determine if it is candidate for termination before incurring the
overhead of swapping it in to find out for sure..
..Paul
|
| True, only some of the GETJPI items require that the process be
active to get the data. Therefore, it is possible to determine
if the process is swapped first, then, if it is not swapped, check
to see if it is idle.
The problem with this is that Zap was designed to free up hardware
resources such as terminal lines which are still being used by a
swapped process. The option is to assume that swapped processes
are always idle, which also may not be true since it may only be
swapped at the moment which Zap scans the system.
The real problem is trying to figure out what to do with swapped
processes?
|