empire/empserver
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Explain why not to edit configs in-place.

Browse source
This commit is contained in:
Markus Armbruster 2006-06-04 12:27:10 +00:00
parent 3aea20e1de
commit 44318648bf
1 changed files with 3 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

5
doc/econfig
View file

@ -73,8 +73,9 @@ Additional customization is possible through key custom_tables, which
is a list of files containing tables in xdump format (see doc/xdump is a list of files containing tables in xdump format (see doc/xdump
for technical information on xdump). To customize a table, copy the for technical information on xdump). To customize a table, copy the
default table from the directory given by econfig key builtindir to a default table from the directory given by econfig key builtindir to a
file next to your econfig, then add the file to custom_keys. Do *not* file next to your econfig, then name the file in custom_tables. Do
edit the default table in-place! *not* edit the default table in-place! That bypasses important
consistency checks.
The server lets you customize more tables than the ones in builtindir. The server lets you customize more tables than the ones in builtindir.
This is not recommended at this time. You can use the xdump command This is not recommended at this time. You can use the xdump command