Gentlemen, can you please not have updateSearchIndex.php write into
the file searchUpdate.pos?
Why?
- Of the thousands of operations on a running Mediawiki wiki, this is
the only one that writes into the local filesystem instead of the
database.
What's wrong with that?
- It precludes using a read only filesystem. If it were not for this
one little 14 byte file, one could use a read only filesystem.
- One might have several wikis using the same files:
radioscanningtw.jidanni.org -> mediawiki-1.11.0
taizhongbus.jidanni.org -> mediawiki-1.11.0
(yes, even the same LocalSettings.php, with appropriate switch()s
inside it.) There is no way two wikis can use the same
searchUpdate.pos.
Also many users might not just untar the updates on top of the
previous file tree, but instead do the much cleaner
tar tzvf mediawiki-1.11.0.tar.tz;
hardlink LocalSettings.php from the old tree to the new;
then move the above symlinks to the new tree;
cd down each symlink to their maintenance dir and php update.php;
Thus searchUpdate.pos will get left behind anyway... (and I wonder what
will happen now that it is left behind?)
Anyway, you have 99.99% reached the goal of a filesystem I/O one-way
clean infrastructure. Please move that tiny "searchUpdate.pos" piece
of information into the database like all the rest of the read/write
information that needs to be more than readonly. Thanks!
P.S., yes, upon initial wiki installation you write into the
filesystem. But writing to the filesystem is totally unnecessary
for running wikis or updating a running wiki.
Version: 1.15.x
Severity: normal