[Tinymux] Upgrading

[Stephen Dennis]

There are three areas that seem to trip people up.

I. Mysterious Setups can haunt your attempts to upgrade.

The first and most likely case is that people have forgotten how they
setup their game, or it is working, but not how they imagine that it
is. Look at mux.config and GAMENAME. The server will look for a
corresponding configuration file called GAMENAME.conf. Inside that
configuration file, you -must- give input_database, output_database,
crash_database, game_dir_file, and game_pag_file which agree with
GAMENAME and DATA in the mux.config file. This is the most common area
of confusion.

Bad things happen if the server @dumps to data/netmux.db.new, but the
./Startmux script is looking for $(DATA)/$(GAMENAME).db.new where
$(DATA) is not "data" and $(GAMENAME) is not "netmux'. Change your
GAMENAME to something else if fine, but remember to change it in every
required place.

So, the first area is that your game may be working mysteriously, but
because you set it up a little off, you will have trouble when it comes
time to update.


II. Unload and verify a flatfile.

./Backup is nifty, but on TinyMUX 2.2, it only works for disk-based
setups. The readme files describe the details. You should be taking
backups already. Make sure that it is a flatfile with attribute values
(not just attribute names).


III. Manually merge your old config file with the new.

There are some additions to the netmux.conf. For example, help files
are turned on there. You need to manually merge your existing
netmux.conf file with the one being distributed. You cannot simply
write over one with the other.

One common question is 'news doesn't work'. Notice that no question
mark was used in this question. Look at 'wizhelp helpfile'. You'll
need 'helpfile news text/news' in your configuration file to turn that
on.

Brazil
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.tinymux.org/pipermail/tinymux/attachments/20051016/8b2c1ca1/attachment.html