Path: utzoo!attcan!uunet!husc6!bloom-beacon!tut.cis.ohio-state.edu!rutgers!bpa!cbmvax!vu-vlsi!mpx1!mpx2!erik
From: erik@mpx2.UUCP (Erik Murrey)
Newsgroups: comp.unix.xenix
Subject: Re: SCO XENIX HoneyDanBer UUCP locking explained
Message-ID: <278@mpx2.UUCP>
Date: 18 Nov 88 05:42:03 GMT
References: <1089@viscous>
Reply-To: erik@mpx2.UUCP (Erik Murrey)
Organization: MPX Data Systems, Inc. ,  Wayne, PA
Lines: 17


[ regarding the fact that the locks are stored in /usr/spool/uucp for
SCO's 2.3.1 HDB-uucp ]

I really wish SCO hadn't done this.  It is a simple define in
uucp.h or param.h that lets the lock files reside in /usr/spool/locks.
This way, only /usr/spool/locks needs to be 0777, and only the
uucp programs need to be setuid.  Kermit, etc, can run normally,
and set the locks in /usr/spool/locks.

This is how the stock 3b2 BNU system did it.

-- 
Erik Murrey                            /|   //  /~~~~/  |  /
MPX Data Systems, Inc.                / | / /  /____/   |/
erik@mpx2.UUCP                       /  /  /  /        /|  Data Systems, Inc. 
{spl1,vu-vlsi,bpa}!mpx1!erik        /     /  /       /  |====================