Path: utzoo!attcan!uunet!amdahl!ames!pasteur!ucbvax!tut.cis.ohio-state.edu!osu-cis!att!chinet!les
From: les@chinet.chi.il.us (Leslie Mikesell)
Newsgroups: comp.unix.questions
Subject: Re: uucp
Message-ID: <7908@chinet.chi.il.us>
Date: 10 Mar 89 23:20:44 GMT
References: <754@oracle.oracle.com>
Reply-To: les@chinet.chi.il.us (Leslie Mikesell)
Organization: Chinet - Public Access Unix
Lines: 16

In article <754@oracle.oracle.com> ehoward@oracle.UUCP (Elliot Howard) writes:

>I know cu and uugetty create a lock file (/usr/spool/lock/LCK..tty* on the
>6386) to keep other processes from using an assigned port. I am also doing
>this, and yet uugetty persists in trying to read and write the tty port at
>the same time I am, causing random characters to go to each process

The lockfile contains the process ID of the program that created it.  HDB
uucp uses an ascii format 10 characters wide with the number right
justified, filled with spaces on the left.  If you find such a lock
file for the port you want, you can tell if the process that created it
is still running by doing a kill(pid,0) and checking the return status
(be sure to check errno to see if the reason for failure is EPERM or
ESRCH).

Les Mikesell