Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!shelby!agate!ucbvax!PAN.SSEC.HONEYWELL.COM!thompson
From: thompson@PAN.SSEC.HONEYWELL.COM (John Thompson)
Newsgroups: comp.sys.apollo
Subject: Minor tcpd quirk
Message-ID: <9102201724.AA06881@pan.ssec.honeywell.com>
Date: 20 Feb 91 17:24:03 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 23

Hi --
    We're running sr10.1 (yuck), sr10.2, sr10.3 (pre-release) and sr10.3 (real).
We also have 10.2p and 10.3p running.  TCP/IP runs on all the nodes.  On all
of the 10.1, 10.2, and 10.3 pre-release systems, the 'tcpd' renames itself
after startup so that it has a name, and not just a uid.  On (real) 10.3 nodes,
though, the 'tcpd' fails to rename itself, and you get
>   1223.716   3/14/14   76088DCC    Wait   uid = 4FCF880B.2002E8EF (tcpd)
when you do a pst.

    This is not a major bug/gripe/whatever.  However, I have a script that 
kills and restarts the tcp services, and I'd rather not have to adjust for 
the different naming behavior of processes.  I suppose I could use the Unix
commands instead, but I know (even if HP doesn't) that Aegis is best.   :-)
Does anyone know why the tcpd process has this new behavior?

tnx
-- jt --
John Thompson
Honeywell, SSEC
Plymouth, MN  55441
thompson@pan.ssec.honeywell.com

Me?  Represent Honeywell?  You've GOT to be kidding!!!