Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!eecae!netnews.upenn.edu!rutgers!bpa!cbmvax!vu-vlsi!mpx1!mpx2!erik
From: erik@mpx2.UUCP (Erik Murrey)
Newsgroups: comp.mail.misc
Subject: Re: Mail locking...
Message-ID: <355@mpx2.UUCP>
Date: 24 Mar 89 03:04:41 GMT
References: <588@dtscp1.UUCP> <548@kl-cs.UUCP> <98@dsinc.UUCP>
Reply-To: erik@mpx2.UUCP (Erik Murrey)
Organization: MPX Data Systems, Inc. ,  Wayne, PA
Lines: 21

In article <98@dsinc.UUCP> syd@dsinc.UUCP (Syd Weinstein) writes:
>In article <548@kl-cs.UUCP> jonathan@cs.keele.ac.uk (Jonathan Knight) writes:
>>From article <588@dtscp1.UUCP>, by scott@dtscp1.UUCP (Scott Barman):
>>> 3.2 system.  I need to know how these systems lock the mail file.
>>> Does /usr/.../*.lock work on both of these?  I know that our v7-like
>
>Ok, here's a quick overview of locking for mail systems:
>Systems that don't use flock() on the spool file itself, use a .lock
>file.  Where that file resides depends on the system.

Actually, the easiest way to tell what kind of locking is used is to
to an "od" or "hd" of the spool directory.  Look for deleted files
that end in .lock or .lck.  Also look at /tmp.  If you don't see any,
then I'll bet they use lockf (SYSV) or flock (BSD).

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