>Number: 3039 >Category: general >Synopsis: MMapFile doesn't do what it should (file edits are read by >server) >Confidential: no >Severity: non-critical >Priority: medium >Responsible: apache >State: open >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Mon Sep 21 15:30:00 PDT 1998 >Last-Modified: >Originator: [EMAIL PROTECTED] >Organization: apache >Release: 1.3.1 >Environment: SunOS 5.6 Generic_105181-05 sum4m sparc SUNW, SPARCstation-5 gcc 2.8.1 >Description: I enabled mod_mmap_static in my Configuration file (everything stayed basically the same, although I also added Apache-SSL and mod_perl).
I used a very simple MMapFile directive, i.e. MMapFile /var/cyberspace.mit.edu/htdocs/index.html This should be the correct path... the DocumentRoot is /var/cyberspace.mit.edu/htdocs and later configuration directives are located within <Directory /var/cyberspace.mit.edu/htdocs>...</Directory> I load the page (using lynx, but browser doesn't seem to make a difference, nor should it). Then, I change it with an in-place edit (just vi or emacs) ... adding "ABCABC" to the last line, for example. Then, I reload the file. The new changed text "ABCABC" appears. According to the docs for mmap_static, this shouldn't happen -- the changes should appear unless I unlink the file (via mv or rm). BTW, the reason I'm trying to produce this "dumb" result is to verify that mmap_static is working. If, for some reason, mmap_static somehow does a stat and checks for an update disk, then I am the "dumb" one. >How-To-Repeat: It's a little tricky, since I'd have to edit the file. If you want to arrange a time to look at the file, and then 5 minutes later load it again, I can set that up... I'm logged on 9 a.m. to 7 p.m. EST, and often later. >Fix: Not really, but then again it's not that serious a problem. In fact, since it looks like "mmap_static" is not a "category" choice above, maybe it's not even supported. If so, sorry for the inconvenience. >Audit-Trail: >Unformatted: [In order for any reply to be added to the PR database, ] [you need to include <[EMAIL PROTECTED]> in the Cc line ] [and leave the subject line UNCHANGED. This is not done] [automatically because of the potential for mail loops. ] [If you do not include this Cc, your reply may be ig- ] [nored unless you are responding to an explicit request ] [from a developer. ] [Reply only with text; DO NOT SEND ATTACHMENTS! ]
