Date: Sat, 25 May 2002 00:40:40 -0700 (PDT) From: Matthew Dillon <dillon@apollo.backplane.com> To: Eugene Grosbein <eugen@svzserv.kemerovo.su> Cc: stable@FreeBSD.ORG Subject: Re: NFS problem with 4.6-PRERELEASE: SIGBUG in Apache Message-ID: <200205250740.g4P7ee6P061752@apollo.backplane.com> References: <3CEE5094.EFF31B42@grosbein.pp.ru> <200205242137.g4OLbFmi058923@apollo.backplane.com> <20020525102224.A43047@svzserv.kemerovo.su> <200205250250.g4P2oSdA060174@apollo.backplane.com> <3CEF1E41.841937F4@svzserv.kemerovo.su>
next in thread | previous in thread | raw e-mail | index | archive | help
:> mv index.html.new index.html
:
:Well, I can try this but I'd like to thing about general approach.
:Perhaps, mmap should fail for files residing on NFS?
:For example, Apache will then switch to another method of reading.
:
:Eugene
You might be able to tell Apache not to use mmap(), but all it will do
is stop apache from seg-faulting. It still won't prevent Apache from
serving up bad file content if it happens to catch the file right in
the middle of someone updating it.
mmap() over NFS works just fine, you simply have to be aware of the
issues related to truncating or deleting the file out from under a
client which is trying to mmap() it.
-Matt
Matthew Dillon
<dillon@backplane.com>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200205250740.g4P7ee6P061752>