Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site down.FUN
Path: utzoo!watmath!clyde!bonnie!akgua!whuxlm!whuxl!houxm!ihnp4!mhuxn!mhuxr!ulysses!allegra!princeton!down!honey
From: honey@down.FUN (Peter Honeyman)
Newsgroups: net.bugs.uucp
Subject: Re: Read permission on /etc/phones
Message-ID: <525@down.FUN>
Date: Thu, 4-Jul-85 12:27:46 EDT
Article-I.D.: down.525
Posted: Thu Jul  4 12:27:46 1985
Date-Received: Sat, 6-Jul-85 09:23:18 EDT
References: <472@qantel.UUCP> <170@motel6.UUCP> <154@telesoft.UUCP>
Organization: Princeton University, EECS
Lines: 11
Keywords: tip, uucp, LCK

a possible solution is to follow honey danber's lock file treatment.
assuming tip's lock files have the same format as uucp's, the lock file
contains the pid of the process that created it.

write a program that reads the lock file and issues signal 0 to the
named pid.  if the return is 0 or EPERM, the lock file is valid,
otherwise it should be removed.  if binary license is a problem, make
tip a shell script that calls tip, then this program.  i leave the
details to your imagination.

	peter