Xref: utzoo comp.unix.xenix:3412 comp.unix.microport:1623
Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!ames!killer!vector!rpp386!pigs!haugj
From: haugj@pigs.UUCP (John F. Haugh II)
Newsgroups: comp.unix.xenix,comp.unix.microport
Subject: kill system call (was: Re: Buggy UUCP)
Message-ID: <430@pigs.UUCP>
Date: 23 Sep 88 15:39:19 GMT
References: <25145@ucbvax.BERKELEY.EDU> <465@sp7040.UUCP> <11643@steinmetz.ge.com> <936@cerebus.UUCP> <7013@icdi10.uucp> <12017@steinmetz.g
Reply-To: haugj@pigs.UUCP (John F. Haugh II)
Organization: Precision Information, Dallas, TX
Lines: 19

In article <8349@bigtex.uucp> james@bigtex.UUCP (James Van Artsdalen) writes:
>Older UUCPs did not use the (relatively new) capability of kill to
>detect the existence of a process, and hence simply assumed that a
>lock was "stale" if it was old enough.  "Old enough" often meant an
>hour or two.  This scheme doesn't [ work ] terribly well.

the kill (PID, 0) idiom has been in unix since 7th Edition days, at
least.  it is common to both BSD and USG unixii, so it can be used
without worrying about portablity.

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.  [ LCK.. files will be removed by uucico if
need be ]
-- 
=-=-=-=-=-=-=-The Beach Bum at The Big "D" Home for Wayward Hackers-=-=-=-=-=-=
               Very Long Address: John.F.Haugh@rpp386.dallas.tx.us
                         Very Short Address: jfh@rpp386
                           "ANSI C: Just say no" -- Me