Xref: utzoo comp.unix.xenix:3420 comp.unix.microport:1637
Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!cs.utexas.edu!utastro!bigtex!james
From: james@bigtex.uucp (James Van Artsdalen)
Newsgroups: comp.unix.xenix,comp.unix.microport
Subject: Re: kill system call (was: Re: Buggy UUCP)
Message-ID: <8422@bigtex.uucp>
Date: 24 Sep 88 14:15:22 GMT
References: <25145@ucbvax.BERKELEY.EDU> <465@sp7040.UUCP> <11643@steinmetz.ge.com> <936@cerebus.UUCP> <7013@icdi10.uucp> <12017@steinmetz.g <430@pigs.UUCP>
Reply-To: james@bigtex.UUCP (James Van Artsdalen)
Organization: F.B.N. Software, Austin TX
Lines: 17

In article <430@pigs.UUCP>, haugj@pigs.UUCP (John F. Haugh II) wrote:

> uuclean should still be set to remove LCK.. files that are more than
> a few hours old so that LCK.. files will be deleted if they
> are abandoned.

uuclean should *>NOT<* remove LCK files unless the locking process is
no longer active.  "a few hours" is certainly not long enough to
ensure that the original process has gone away - I've had uucico
sessions last upwards of eight hours (during news floods).  If uuclean
removes an active LCK and the remote's uuclean does likewise, you're
quite likely to have a second set of uucico's start up a second
session, resulting in duplicate mail or news and a probable ASSERT
error once the two uucico's start removing each other's [CD]. files.
-- 
James R. Van Artsdalen	...!uunet!utastro!bigtex!james	"Live Free or Die"
Phone: 512-346-2444		  10926 Jollyville Rd #901 Austin TX 78759