You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@spamassassin.apache.org by bu...@bugzilla.spamassassin.org on 2004/04/05 20:26:43 UTC
[Bug 3241] New: nfsunlock function required
http://bugzilla.spamassassin.org/show_bug.cgi?id=3241
Summary: nfsunlock function required
Product: Spamassassin
Version: SVN Trunk (Latest Devel Version)
Platform: Other
OS/Version: other
Status: NEW
Severity: normal
Priority: P5
Component: Libraries
AssignedTo: spamassassin-dev@incubator.apache.org
ReportedBy: jm@jmason.org
Alexis Rosen <alexis at panix.com> sez:
> >Hey, guys. I'm just following up because I'm curious about the final
> >disposition of the nfslock code. Did you add a function to correspond to
> >nfsunlock? I hope the rest of my comments were helpful.
>
> Actually, we haven't :( It dropped off my radar, unfortunately.
>
> I'm thinking we should take a look at that before 3.0.0 release, and
You *really* should.
> OK, here's the source. It's attached (only ~10k). A few things to think about:
>
> - Some of the issues involved are *really* subtle. Don't throw out the sleep
> in nfsunlock, for example.
> - The race condition that made me write nfsunlock may seem a virtual
> impossibility, but if you are actually running across NFS, it's not the most
> unlikely thing in the world. All you need is a small network problem at the
> wrong time.
> - nfs{,un}lock4 was written to deal with a bug in netbsd. It had a hideously
> broken nfs client that didn't act atomically even for link(). Nothing you
> can do about that except work around it as best you can. I encourage you to
> NOT use this workaround- it's very expensive, and the problem no longer exists,
> I think. nfstest is a tiny bit of code that can turn up systems with that
> problem. I know of no other Unixes that have that problem.
code at:
http://mail-index.netbsd.org/netbsd-bugs/1996/04/17/0002.html
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.