Path: utzoo!attcan!uunet!lll-winken!ncis.llnl.gov!helios.ee.lbl.gov!pasteur!agate!bionet!csd4.milw.wisc.edu!uxc!uxc.cso.uiuc.edu!uxg.cso.uiuc.edu!uicsrd.csrd.uiuc.edu!kai
From: kai@uicsrd.csrd.uiuc.edu
Newsgroups: comp.unix.wizards
Subject: Re: Hard Links Considered Not Harmful (
Message-ID: <43200063@uicsrd.csrd.uiuc.edu>
Date: 19 Jan 89 01:13:00 GMT
References: <5437@phoenix.Princeton.EDU>
Lines: 23
Nf-ID: #R:phoenix.Princeton.EDU:5437:uicsrd.csrd.uiuc.edu:43200063:000:931
Nf-From: uicsrd.csrd.uiuc.edu!kai    Jan 18 19:13:00 1989


> You can configure deliver to use any combination of kernel locking and/or
> file creation locking, and you can vary delivery behavior based on just
> about anything.  Fcntl() or lockf(), for example.

This brings up a problem that I've run into before.  How do you lock
something that is located on an remote NFS file system?  Some people here
would like to have their mail delivered to a random directory instead of
/usr/spool/mail/<userid>.  Other people would like to be able to read mail
from any machine.  This requires some other locking mechanism.

Suns have some kind of specialized daemon, but that isn't generally
available.  Are lockfiles the only thing left?  Does anyone has something
that is the equivalent of a network flock?


Patrick Wolfe
System Manager, Kuck & Associates
pat@kai.com
{uiucuxc,sequent,alliant,uunet}!kailand!pat
pat@kai.com@uiucvmd.bitnet
pat%kai.com@uxc.cso.uiuc.edu
pat%kai.com@uiucuxc.arpa