Chuck asks:

> Instead of raising it to the B Queue where it could interfere with system
>  processes, could you not use the altproc command to peg it at the top of
the
>  C queue?
>
>  As in: altproc job=#j2;pri=152
>
>  Where 152 is the top priority of the C queue.
>
>  Or I am misunderstanding this?

Although I've never noticed any interference with anything on the HP3000 by
putting JINETD into the B queue, anything that you might do to get JINETD off
of the floor of the C queue would have to be to the good. JINETD simply has
to get a fair shot at some processor time on a very busy machine if new users
are to get a logon prompt.

But, as I say, the busy-ness of the machine only affects the time that it
takes for new users to see logon prompts. Currently logged on telnet sessions
are unaffected by CPU busy-ness, other than the obvious manner that all
sessions are affected.

Wirt Atmar

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