Ted Ashton writes:
>
> Thus it was written in the epistle of Götz Neumann,
>
> <snip>
>
> > - I raise the priority of non-aborting jobs with
> >   :ALTPROC JOB=...;PRI=CS
> >   since termination code runs on the processes behalf
> >   itsself and may simply need to get some CPU on a busy
> >   system.
> > (potential for an enhancement request here, have ABORTJOB
> > do that automagically)
>
> Yup.  Could someone at HP say if this would be a doable thing?  It might have
> unexpected unwanted side effects, in which case, lets leave it alone.  If not,
> though, it would be nice to have.

This would be a Bad Thing if you had to abort a process stuck in a loop deep
in system code.  If it turned out to be an un-:ABORTJOBable problem, your hard
CPU loop would now severely impair the rest of your system if the priority were
automatically raised.

I had such an unabortable loop problem with FTP a few months ago (subsequently
fixed by a patch).  The loop would consume all available CPU, so I had to
alter the priority all the way down to L255 to keep the CPU hog out of the way
until I could reboot later that night.
--
Mark Bixby                      E-mail: [log in to unmask]
Coast Community College Dist.   Web: http://www.cccd.edu/~markb/
District Information Services   1370 Adams Ave, Costa Mesa, CA, USA 92626-5429
Technical Support               Voice: +1 714 438-4647
"You can tune a file system, but you can't tune a fish." - tunefs(1M)