Xref: utzoo comp.unix.xenix:3444 comp.unix.microport:1658
Path: utzoo!utgpu!water!watmath!clyde!att!rutgers!mailrus!cornell!batcomputer!itsgw!steinmetz!davidsen
From: davidsen@steinmetz.ge.com (William E. Davidsen Jr)
Newsgroups: comp.unix.xenix,comp.unix.microport
Subject: Re: kill system call (was: Re: Buggy UUCP)
Message-ID: <12242@steinmetz.ge.com>
Date: 26 Sep 88 19:49:13 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> <8422@bigtex.uucp>
Reply-To: davidsen@crdos1.UUCP (bill davidsen)
Organization: General Electric CRD, Schenectady, NY
Lines: 21

In article <8422@bigtex.uucp> james@bigtex.UUCP (James Van Artsdalen) writes:
| 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).

  As John says "if abandoned". I don't remember how or if uuclean
checks, but the "unlock" program I posted some time ago does just what
you say. I run it just before all scheduled executions of uucico, since
I had a problem with an old version of uucico which ocasionally just
"went away".
-- 
	bill davidsen		(wedu@ge-crd.arpa)
  {uunet | philabs}!steinmetz!crdos1!davidsen
"Stupidity, like virtue, is its own reward" -me