Update for recent pconfig changes.
This commit is contained in:
parent
5b57f4c222
commit
a53c6e74c4
1 changed files with 2 additions and 6 deletions
|
@ -17,10 +17,10 @@ Deity Notes
|
|||
|
||||
To find out the current configuration, the simplest method is to
|
||||
compile up util/pconfig and the run it. It can be run either with no
|
||||
arguments, in which case it will printout in config format the current
|
||||
arguments, in which case it will print in config format the current
|
||||
compiled in options. Otherwise with a file containing a configuration
|
||||
it will first read in this file, and override any compiled in
|
||||
variables and then printout the merged options.
|
||||
variables and then print the merged options.
|
||||
|
||||
So the first method shows you what's compiled in, the 2nd how a config
|
||||
file would modify this.
|
||||
|
@ -60,10 +60,6 @@ To turn off an option that is compiled in, you can similarly have
|
|||
or
|
||||
nooption FUEL ORBIT
|
||||
|
||||
|
||||
As a check, pconfig will printout some of the internal file names as
|
||||
comments at the end just to check they are in the right place.
|
||||
|
||||
The server can take a -e config file as a command line option so that
|
||||
it will read a specific config file. If not, it will default to
|
||||
looking for a file econfig in the built in data directory, but it
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue