Hello Eva Pattison & friends @ 3000-l,

Re: INETD Ftp & Telnet hangs fixed

------------------------------------------------------------ Eva Writes --
Hi. Question about the hangs.  I'm trying to find out if this is a similar
problem some users have with our system.  Can you tell me if this is what
you are talking about?  Some, not all, of our users hang while connected
via Telnet  I haven't been able to figure out why.  The users that get
hung, do not experience the problem if the first Telnet to a UNIX machine
and then Telnet to the 3000.  If they Telnet directly to the 3000, they
most times get hung and have to disconnect.Is that similar to what you say
is fixed with <Patch?>. Thanks.  Eva
------------------------------------------------------------ Eva Writes --

These symptoms do not give me enough information to guess if the problem
you are seeing is the same as fixed in the patch...

The most common problem seen with Telnet is establishing initial connections
and these problems are mostly seen when the CPU is in a busy state.

The most frequent problem is INETD starvation since JINETD is a batch job
and as default runs in the DS queue.  The first action the Response Center
will likely take is to check to see if you have the priority of INETD moved
to the CQ by modifying line to to include ";pri=cs".  In rare cases on very
busy/slow machines we have achieved results by specifying ";pri=152" (top of
the CQ).

/t jinetd.net.sys
FILE UNNUMBERED
/l all
    1     !job jinetd, manager/?.sys/?
    2     !run inetd.net.sys;pri=cs
    3     !eoj

Secondly fixes have gone into the latest Telnet patches PTDFDK0 5.5 and
PTDFDK2 6.0 which address Telnet and FTP hangs out of PTID_INIT.

If you believe your hangs could be associated with Telnet and Typeahead,
the PTDFDK0 5.5 and PTDFDK2 6.0 patches include fixes to several problems
seen in typeahead over Telnet.  Do not pass go, do not collect 200 dollars,
if you are suspect of a typeahead problem over Telnet, install the latest
Telnet PTD patch.

Finally as painful as it sounds, a memory dump may be necessary to
identify the root cause of a Telnet session hang.

I hope this helps.

Regards,

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