From: larry@shiva.eco.twg.com (Lawrence B. Henry III)
Subject: Re:      How To Shutdown WIN/TCP?
Reply-To: larry@eco.twg.com
Organization: The Wollongong Group (East Coast Operations)
Date: Wed, 18 Nov 92 00:49:25 GMT


In article <01GQZNV2133I94DNJU@OREGON.UOREGON.EDU>,         Rick Millhollin <RICKM@OREGON.BITNET> writes:
|>Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
|>Path: eco.twg.com!uunet!stanford.edu!agate!spool.mu.edu!darwin.sura.net!paladin.american.edu!auvm!OREGON.BITNET!RICKM
|>X-Delivery-Notice:  SMTP MAIL FROM does not correspond to sender.
|>X-Envelope-to: wintcp-l@ubvm.bitnet
|>X-VMS-To: in%"wintcp-l@ubvm.bitnet"
|>MIME-version: 1.0
|>Content-transfer-encoding: 7BIT
|>Message-ID: <01GQZNV2133I94DNJU@OREGON.UOREGON.EDU>
|>Newsgroups: vmsnet.networks.tcp-ip.wintcp
|>Date:         Tue, 10 Nov 1992 14:47:48 -0800
|>Sender:       Wollongong TCP/IP Discussion List <WINTCP-L@UBVM.BITNET>
|>From:         Rick Millhollin <RICKM@OREGON.BITNET>
|>Subject:      How To Shutdown WIN/TCP?
|>Lines: 37
|>
|>We are having a problem with system shutdown and WIN/TCP.  When up and running,
|>WIN/TCP processes have files open on the disk where it is installed, which is
|>actually a shadow set.
|>
|>$ show device/files sys$netdevice
|>
|>Files accessed on device DSA62: on 10-NOV-1992 14:29:41.65
|>
|>Process name      PID     File name
|>...
|>enet<->inet     20200121  [WINTCP.V52.OREGON.NETDIST.MISC]ELINKUP.COM;2
|>enet<->inet     20200121  [WINTCP.V52.COMMON.NETDIST.ETC]ELINK.EXE;1
|>NAMED           20200122  [WINTCP.V52.OREGON.NETDIST.MISC]NAMEDUP.LOG;98
|>NAMED           20200122  [WINTCP.V52.COMMON.NETDIST.MISC]NAMEDUP.COM;3
|>NAMED           20200122  [WINTCP.V52.COMMON.NETDIST.ETC]NAMED.EXE;1
|>INET_SERVERS    20200123  [WINTCP.V52.COMMON.NETDIST.SERV]SERVER.EXE;2
|>TALKD           20200124  [WINTCP.V52.COMMON.NETDIST.MISC]TALKDUP.COM;1
|>TFTP_DAEMON     20200125  [WINTCP.V52.COMMON.NETDIST.SERV]TFTPD.EXE;1
|>NTP_DAEMON      20200126  [WINTCP.V52.COMMON.NETDIST.MISC]NTPDUP.COM;1
|>TALKD           20200124  [WINTCP.V52.COMMON.NETDIST.ETC]TALKD.EXE;1
|>NTP_DAEMON      20200126  [WINTCP.V52.COMMON.NETDIST.SERV]NTPD.EXE;1
|>NTP_DAEMON      20200126  [WINTCP.V52.COMMON.NETDIST.ETC]NTPD.CONF;2
|>...
|>
|>If this system is shut down, the shadow set does not get dismounted properly
|>because some of these processes do not get stopped so the files do not get
|>closed.  This causes the shadow set to go into mount verification on the rest of
|>
|>the cluster, and a shadow merge to take place.
|>
|>I have put a procedure into SYSHUTDWN.COM to look for the WIN/TCP processes and
|>STOP them.  However, it appears that frequently enet<->inet holds an
|>IOC$GL_MUTEX (according to DEC's analysis of a dump we forced) and so can't
|>stop, thus hanging the shutdown.
|>
|>What I need is a clean and sure-fire method to shut down WIN/TCP from
|>SYSHUTDWN.COM.  Is there one?
|>

DEC's analysis seems pretty suspect.. especially considering we don't hold
that mutex in that program.. But we will mail you a copy of a procedure that we
use in-house.. If there are others who would like a copy send me mail..

It has long been my desire to supply a single program to handle
such events as this..ie, shutdown the network.. as part of an upcoming 
release on a recently announced DEC platform we will be including
such a utility..

-Larry.