Xref: utzoo comp.unix.xenix:3402 comp.unix.microport:1611
Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!uwmcsd1!marque!uunet!mcvax!unido!quando!biburger
From: biburger@quando.UUCP (Wolf-D. Biburger)
Newsgroups: comp.unix.xenix,comp.unix.microport
Subject: Re: Buggy UUCP (was: Re: Bell Tech 386 SysVr3)
Message-ID: <641@quando.UUCP>
Date: 22 Sep 88 03:36:20 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> <394@marob.MASA.COM> <193@dcs.UUCP>
Reply-To: biburger@quando.UUCP (Wolf-D. Biburger)
Organization: Quantum GmbH, Dortmund, W-Germany
Lines: 23

In article <193@dcs.UUCP> wnp@dcs.UUCP (Wolf N. Paul) writes:
>In article <394@marob.MASA.COM> daveh@marob.masa.com (Dave Hammond) writes:
>>In article <385@pigs.UUCP> haugj@pigs.UUCP (Joe Bob Willie) writes:
>>(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.
the problem may also occur, if those programs (kermit etc.)
place the 'LCK..'-files in '/usr/spool/uucp/' but 'uucico'
in '/usr/spool/uucp/LCK/'

>I believe that's because of the way UUCP-related programs determine the
>validity of lock files.
I don't think so - there are instructions inside the programs, to
check the existance of the 'LCK..'-file, but not any contents of it.
those 'LCK..'-files work as a semaphor (see the name....) and
if they exist a long time there may get up a 'uuclean'-process,
to check the age of all files in '/usr/spool/uucp/' see '..../crontab'

-- 
					"Wolf-Dieter Biburger"
Uad- biburger@quando.UUCP
Off- Quantum GmbH / E-Figge-Str. 83 / D-4600 Dortmund 50 / (49) +231 75 44 1 00
Prv- Am Spoerkel 61 / D-4600 Dortmund 50 / +231 75 41 03