Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!wuarchive!uunet!bu.edu!att!ucbvax!RICHTER.MIT.EDU!krowitz
From: krowitz@RICHTER.MIT.EDU (David Krowitz)
Newsgroups: comp.sys.apollo
Subject: Re:  TCP/IP hangup
Message-ID: <9102111537.AA10181@richter.mit.edu>
Date: 11 Feb 91 15:37:12 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 30

First of all, the Apollo file services (ie. cd //my_apollo) do
not require TCP/IP. The Apollo file system uses it's own network
protocals which are independent of the TCP/IP protocals.

Your problem is that the /etc/tcpd TCP/IP daemon is dying for some
unknown reason. When it goes away, many of the other servers which
rely upon TCP/IP will also die (ie. sendmail, nfs, telnet, rlogin,
ftp, etc.). Apollo-specific services like CRP/SPM and the MBX helper
are not affected, since they use the same protocal suite as the
Apollo file system. You can generally fix the TCP/IP problem by
simply loggin in as "root" and running the /etc/tcpd program by
hand. It will run for a few seconds, and then fork off a copy to
run in the background as a server process. You can also use the
DM's "ex" command to exit from the DM and kill all of the servers
running on the machine *except* for the Apollo file-system servers
and then use the level-2 shell's "go" command to reload all of
the normal servers that are started by the /etc/rc, /etc/rc.local,
and /etc/rc.user shell scripts at boot time. Using, "ex" and then
"go" will usually kill all jobs running on the local machine without
affecting other Apollo users whose files are on the local disk, and
will usually get the machine's servers up and running cleanly (unless
something in the Domain/OS kernal has gone belly-up :-{ ).


 -- David Krowitz

krowitz@richter.mit.edu   (18.83.0.109)
krowitz%richter.mit.edu@eddie.mit.edu
krowitz%richter.mit.edu@mitvma.bitnet
(in order of decreasing preference)