Path: utzoo!utgpu!cunews!bnrgate!brchh104!brchs1!bnr.ca!rice.edu!sun-spots-request
From: jms@tardis.tymnet.com (Joe Smith)
Newsgroups: comp.sys.sun
Subject: Re: The LOCK FILE that doesn't
Keywords: Miscellaneous
Message-ID: <3792@brchh104.bnr.ca>
Date: 12 Jun 91 19:40:00 GMT
Sender: news@brchh104.bnr.ca
Organization: Sun-Spots
Lines: 20
Approved: Sun-Spots@rice.edu
X-Original-Date: Wed, 5 Jun 91 19:41:28 PDT
X-Sun-Spots-Digest: Volume 10, Issue 106, message 12
X-Note: Submissions: sun-spots@rice.edu, Admin: sun-spots-request@rice.edu

In article <3556@brchh104.bnr.ca> karln!uunet.uu.net!karln@uunet.uu.net writes:
>	SYSTEM: Sun SS2, SunOS 4.1.1, OW2.0 etc etc.
>	PROGRAMS: uucp, cu, pcomm
>	SUMMARY: The lock file created by pcomm is ignored by uucp.
>		 The lock file created by cu works well with uucp.
>	I have the pcomm program owned by uucp. Pcomms mode is "..s..x..x", 
>ie, I have the SETUID bit set. The lock file gets created by pcomm, 
>a ls -aldg * looks like this:
>.r..r..r	uucp	staff	LCK..cua1
>but uucp ignores it, erases it and takes over my modem. @#$% !!!!

You did not say which directory pcomm is putting the lock into.
SunOS-4.1.1 uses HDB-uucp, which puts its locks in /var/spool/locks
instead of /var/spool/uucp. 

Joe Smith (408)922-6220 | SMTP: jms@tardis.tymnet.com or jms@gemini.tymnet.com
BT Tymnet Tech Services | UUCP: ...!{ames,pyramid}!oliveb!tymix!tardis!jms
PO Box 49019, MS-C51    | BIX: smithjoe | CA license plate: "POPJ P," (PDP-10)
San Jose, CA 95161-9019 | humorous dislaimer: "My Amiga 3000 speaks for me."