Hello Ron Burnett, 3000-l friends,

Re: Re: JINETD/Telnet Error Messages

--------------------------------------------------------Ron Burnett writes--
The evidence doesn't agree with you.  I raise JINETD's priority (with
ALTPROC JOB=#Jnnnn;PRI=CS) every time I start it up.  One of these
days I'll remember to edit the job file to logon with CS priority.

AND, note from my original message--the error message continues to be
displayed during the night, when the system is otherwise bone idle (although
less frequently than during the day when there are up to 6 or so interactive
sessions).

The system has a OS user limit of 8 users.  Could that be the problem?

I'm puzzled also by the fact that the error condition appears to have no
impact on our ability to get sessions.

Ron Burnett
[log in to unmask]
--------------------------------------------------------Ron Burnett writes--

As I have said, from "my" experience, I have only seen this problem/error
message associated with cpu starvation...  So, if you are seeing something
different, it is time to do further investigation.  I would suggest you
start by looking at the MPE and NM logfiles for the same time you are seeing
the error message and see if you can correlate something from the logging
to the error from INETD.  You may also want to check that you are running
the current General Release patches for telnet "PTD" and ns-transport "NST".

Regards,

James Hofmeister
Hewlett Packard
Worldwide Technology Network Expert Center
P.S. My Ideals are my own, not necessarily my employers.