Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!olivea!uunet!zaphod.mps.ohio-state.edu!unix.cis.pitt.edu!gvlf3.gvl.unisys.com!lgnp1.ls.com!candle!root
From: root@candle.uucp (Bruce Momjian)
Newsgroups: comp.unix.internals
Subject: Re: uugetty respawning
Message-ID: <1991May24.155552.19129@candle.uucp>
Date: 24 May 91 15:55:52 GMT
References: <1991May24.155354.18991@candle.uucp>
Organization: private system
Lines: 20


I am using AT&T 386 Unix 3.1.  When cu and uucp use the modem, they respawn
uugetty.  When Pcomm 1.2 uses the modem, it does not respawn uugetty, and 
the next time someone tries to log in, they get a connect but no login prompt.

To fix this, I currently run pcomm from a script, which also calls
another script with set-uid to root and which executes:

UUPID=`/bin/ps -ef |\
	/bin/grep " *root.*uugetty[^x]*$" | \
	/bin/sed 's/^.*root *\([0-9]*\).*$/\1/'`
if [ "$UUPID" -gt "1" ]
	then	/bin/kill $UUPID
fi

... which kills the uugetty ( I only have one uugetty running) and respawns. 
Obviously, this is a kludge.  

Does anyone know how cu and uucp respawn the uugetty properly, so I may add
this to the pcomm source.  (BTW, is there a more recent pcomm than 1.2).