Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!samsung!uakari.primate.wisc.edu!dali.cs.montana.edu!milton!newton!lgy From: lgy@phys.washington.edu (Laurence G. Yaffe) Newsgroups: comp.sys.mips Subject: Re: uugetty and /usr/spool/locks Message-ID: Date: 14 Jan 91 00:44:14 GMT References: <9101111107.AA09005@fernwood.mpk.ca.us> Sender: news@milton.u.washington.edu Lines: 24 jns@fernwood.mpk.ca.US (Jerry Sweet) writes: -For me, this note applies to RISC/os 4.51 on an RC3230. -The man page for uugetty, as well as the Nutshell handbook, leads one -to believe that uugetty will "step aside" for other processes that -wish to use a modem port for which a uugetty process is awaiting login -(presumably via "respawn" in the inittab). This appears not to be the -case. Uugetty, while waiting for login, leaves a lock file in -/usr/spool/locks. -The question is: how does one properly make the alleged "step-aside" -feature of uugetty happen? [Various possibilities deleted] I posted the same query about 6 months ago and someone (I forget who - sorry!) reminded me that uugetty's from versions of RISC/os earlier than 4.50 seem to work better than the current released version. I believe I'm now using a 4.31 version. -- -------------------------------------------------------------------------- Laurence G. Yaffe Internet: lgy@newton.phys.washington.edu University of Washington Bitnet: yaffe@uwaphast.bitnet