Xref: utzoo comp.unix.xenix:3189 comp.unix.microport:1458
Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!nrl-cmf!cmcl2!phri!marob!daveh
From: daveh@marob.MASA.COM (Dave Hammond)
Newsgroups: comp.unix.xenix,comp.unix.microport
Subject: Re: Buggy UUCP (was: Re: Bell Tech 386 SysVr3)
Message-ID: <394@marob.MASA.COM>
Date: 1 Sep 88 19:22:30 GMT
References: <25145@ucbvax.BERKELEY.EDU> <465@sp7040.UUCP> <11643@steinmetz.ge.com> <936@cerebus.UUCP> <7013@icdi10.uucp> <12017@steinmetz.g <385@pigs.UUCP>
Reply-To: daveh@marob.masa.com (Dave Hammond)
Organization: ESCC  New York City
Lines: 22

In article <385@pigs.UUCP> haugj@pigs.UUCP (Joe Bob Willie) writes:
>i am currently having trouble on three systems i administer with LCK..
>files for the terminals getting nuked.  one of the systems runs the
>"telebit" uucp.  the others don't (because they don't run xenix).

Funny you should mention nuked LCK.. files. I just began noticing the
same thing on a system which just got updated with the TeleBit uucp.
In this case the problem occurs when non-uucp communications programs
(such as Kermit, ProComm or `CU') placed the LCK.. files there. The
new uucico (having been started from some daemon) seems to disbelieve
these `foreign' LCK.. files and unlinks them.

I've also noticed a nasty little `feature' of both the TeleBit and
older uucico programs. If the aforementioned foreign comm program
has set a lock on tty1a, and uucico is started up on tty1A -- you
will see a quick `+++' and then an `ATH0', and you find yourself
staring at `NO CARRIER'. Hmmm.

Dave Hammond
  UUCP: {uunet|...}!marob.masa.com!!daveh
DOMAIN: daveh@marob.masa.com
------------------------------------------------------------------------------