*BSD News Article 27591


Return to BSD News archive

Newsgroups: comp.os.386bsd.questions
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!purdue!mentor.cc.purdue.edu!PURCCVM.BITNET!BORMANN
From: BORMANN@PURCCVM.BITNET (Bill Bormann)
Subject: NFS locking in FreeBSD 1.0e
Message-ID: <16F6363A8S85.BORMANN@PURCCVM.BITNET>
Keywords: lockf(), flock(), mh
Sender: news@mentor.cc.purdue.edu (USENET News)
Organization: Purdue University
Date: Sun, 20 Feb 1994 12:05:12 GMT
Lines: 19

I'm trying to bring up mh 6.8.3 on my system running FreeBSD 1.0e but
ran into a hitch compiling the routine lock.c.
 
The problem is that I mount the mail spooling directory -t nfs, so in
the configuration options for mh I selected LOCKF (kernel level locking).
This did not compile.  When I try to select FLOCK I get an error message
indicating the FLOCK feature is not available.
 
A quick peruse through the FreeBSD source code suggests that file
locking is not really needed by mh since this detail is handled by the
nfs code in the kernel.  Unfortunately, I am a green newbie reading
FreeBSD os code, and would like someone to confirm my suspicions ...
 
My question is quite simply, do I need to worry about file locking for
nfs mounted file systems?
 
Bill Bormann                 | Math Sciences Building
bormann@purccvm   (BITNET)   | Purdue University Computing Center
ad2@cc.purdue.edu (Internet) | West Lafayette, IN 47907