Xref: utzoo comp.os.vms:7755 comp.sys.dec:729
Path: utzoo!utgpu!attcan!uunet!husc6!rutgers!ucsd!orion!iglesias
From: iglesias@orion.cf.uci.edu (Mike Iglesias)
Newsgroups: comp.os.vms,comp.sys.dec
Subject: Re: Wollongong WIN/TCP Problem: No automated procedure to stop the process
Keywords: Win/tcp
Message-ID: <928@orion.cf.uci.edu>
Date: 3 Aug 88 20:51:10 GMT
References: <292@versatc.UUCP>
Reply-To: iglesias@orion.cf.uci.edu (Mike Iglesias)
Organization: University of California, Irvine - Computing Facility
Lines: 30

In article <292@versatc.UUCP> tran@versatc.UUCP (Tony Tran) writes:
>Under Wollongong Win/TCP V3.0 or 3.2, there is no command procedure or program
>to stop the Wollongong software. According to katie@twg.com (Wollongong Tech
>Support), you have to do something like:
>
>	1. ifconfig ep0 down
>	2. Do a "show system", and issue the command: "stop/id=xxx" where xxx
>	   are the process id of enet <-> inet and INET_SERVERS processes
>	3. Kill any ftp users processes
>
>Has anybody developed any command procedure that automatically stops the Wollongong
>software, something like stopinet.com ?
>
>I have defined a symbol that orderly shuts down the VAX, but can't seem to
>incorporate the above features, and as a result, doesnot *cleanly* shutdown
>the VAX (when I forget to do the 3 items above manually).

In the year or two I've been running WIN/TCP, I've never had to do anything
special to shutdown WIN/TCP when shutting down the VAX.  I've used
WIN/TCP v2.3 thru v3.2 and several versions of VMS.  Just do whatever
you need to do and run SYS$SYSTEM:SHUTDOWN.COM.  If you want to be
somewhat orderly, ifconfig ep0 down.  After all, you're going to shut
the system down, so who cares if enet <-> inet and INET_SERVERS is
still running?  You can can always write a DCL command script or
program to find enet <-> inet and INET_SERVERS and kill them off,
but it sounds like a waste of programmer time to me.


Mike Iglesias
University of California, Irvine