Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!mit-eddie!ll-xn!ames!aurora!labrea!decwrl!pyramid!uccba!hal!ncoast!allbery
From: allbery@ncoast.UUCP (Brandon Allbery)
Newsgroups: comp.sys.att
Subject: Re: UUCP on 3B1
Message-ID: <5314@ncoast.UUCP>
Date: Sat, 7-Nov-87 18:38:04 EST
Article-I.D.: ncoast.5314
Posted: Sat Nov  7 18:38:04 1987
Date-Received: Wed, 11-Nov-87 02:10:15 EST
References: <1007@csustan.UUCP> <9300026@bradley>
Reply-To: allbery@ncoast.UUCP (Brandon Allbery)
Followup-To: comp.sys.att
Organization: Cleveland Public Access UN*X, Cleveland, Oh
Lines: 21

As quoted from <9300026@bradley> by ninja@bradley.UUCP:
+---------------
| I had the same problem with mine.  Very irritating when you trust uucp
| to hang up your phone.  It didn't complete the call successfully, and
| I gave up in disgust.   I went to use my phone about 2 hours later and
| it was off-hook; thanks AT&T.  I also noticed that in general the 3B1
| loves to grab a phone line entirely (you can't pick up your phone to
| listen and see if it's dialing, or if it's transfering data).  
+---------------

I've had it happen too; recovery is simply doing a "ps -ef", noticing that
there is a setgetty hung, and killing the setgetty.  THIS IS BOGUS!!!  Is
there some way that I can inform the Phone Manager that I *never* want a getty
on the phone line?  (My machine is not dial-in, and I won't be making it
dial-in.)  Just renaming setgetty won't work (and neither does replacing
it with a C program which does nothing but exit(0)); cu, at least, reports
"requested device not known" after this.
-- 
Brandon S. Allbery		     necntc!ncoast!allbery@harvard.harvard.edu
 {harvard!necntc,well!hoptoad,sun!mandrill!hal,uunet!hnsurg3}!ncoast!allbery
Moderator of comp.sources.misc