Subject: | |
From: | |
Reply To: | HOFMEISTER,JAMES (HP-USA,ex1) |
Date: | Wed, 20 Mar 2002 21:21:11 -0800 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
hello 3000-l,
Re: JINETD process
>>Our JINETD job keeps spinning out of control. It will run fine for hours,
>>days, weeks, then act like this. It's taking all the CPU even in the E
>>queue. Anyone seen this before?
As suggested, start with the GR patches:
INTFDX2 for C.60.00
NSTGD19 for C.60.00
FTPGD91 for C.60.00 (if you configure/use FTP)
PTDGD17 for C.60.00 (if you configure/use TELNET)
In the JINETD.NET.SYS job:
:print jinetd.net.sys
!job jinetd, manager/pass.sys/pass
!run inetd.net.sys
!eoj
1) Do not specify "-l" logging.
2) Do not specify ";pri=". The correct priority for INETD is coded in the
INTFDX2 patch.
If you see problems beyond this, it is important to work with the HP
Response
Center to get multiple stack traces of the INETD.NET.SYS process while it is
looping to determine what code it is looping in and determine further if
root
cause can be identified.
Regards,
James Hofmeister
Hewlett Packard
Worldwide Technology Network Expert Center
P.S. My Ideals are my own, not necessarily my employers.
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|
|
|