Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msunews!uwm.edu!math.ohio-state.edu!howland.reston.ans.net!xlink.net!zib-berlin.de!news.tu-chemnitz.de!irz401!narcisa.sax.de!not-for-mail
From: j@narcisa.sax.de (J Wunsch)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: elm 2.4 and FreeBSD 2.0
Date: 12 Jun 1995 11:20:01 +0200
Organization: Private U**x site, Dresden.
Lines: 22
Message-ID: <3rh0s1$ljn@bonnie.tcd-dresden.de>
References: <D82tBw.Fzs@ct.covia.com> <3qmrmk$9dg@helios.cto.us.edu.pl> <3r177b$fqk@bonnie.tcd-dresden.de> <3r3vq0$jk9@helios.cto.us.edu.pl>
Reply-To: joerg_wunsch@uriah.heep.sax.de
NNTP-Posting-Host: 192.109.108.139
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Witold Swierzy <swierzy@tc3.ich.us.edu.pl> wrote:
>
>: ... But this is (IMHO) _not_ related to the lock file locking
>: method in question here. The latter is done in the mail spool, and
>: it's the only method allowing to lock the mail spool file if it's NFS
>: mounted between several machines (which usually don't have a shared
>: /tmp).
>It is possibly that You're right, but my machine doesn't work as a
>NFS server or client - so dot-style locking is enough for me.
You misunderstood me. Dot-style locking is **only** useful for NFS
shared mail spools. Any normal configuration should prefer flock() or
fcntl() locking (internally the same), the locking is performed by the
kernel then.
Lock files are always ugly.
--
cheers, J"org private: joerg_wunsch@uriah.heep.sax.de
http://www.sax.de/~joerg/
Never trust an operating system you don't have sources for. ;-)