HP3000-L Archives

March 1996, Week 4

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Eero Laurila <[log in to unmask]>
Reply To:
Eero Laurila <[log in to unmask]>
Date:
Mon, 25 Mar 1996 01:07:59 GMT
Content-Type:
text/plain
Parts/Attachments:
text/plain (30 lines)
Hi network dudes and dudettes,  there's an updated version of the SHOWCONN
utility on http://jazz.external.hp.com for you to pick up.  There's a one
for 5.0 systems and another for 5.5.  With the 5.5 version you get also the
source code.
 
ABORTCON is a superset of NSCONTROL KILLSESS, i.e. it will work on VTSERVERs
exactly the same as NSCONTROL KILLSESS does, however, in addition to that
it will work on any process that has a TCP connection.  ABORTCON has two
parameters, one for real work and another for version reporting.  Syntax
is pretty simple:
 
   :ABORTCON [pin=] <pin_number>
 
When invoked as above, abortcon will run the program SC.PUB.SYS, which will
locate the process in question and abort all it's TCP connections.  Usually
this results on the process in question terminating.  At least, the socket
will become unusable and depending on what the application has been coded to
do on a network error, that should follow.  For most network applications
any socket error is fatal and usually the application in question terminates.
This is the case for all NS services, FTP, telnet, database access servers
and so on - they all terminate on a network error.  Of course, there may
be processes that behave differently - for example the new network spooler
on the HP 3000 will not terminate, it'll just invoke network error recovery
routines and try to reconnect.
 
Have fun and pls let me know how it works for you.
 
Thanx,
Eero - HP CSY Networking lab, NS services.

ATOM RSS1 RSS2