This gives a brief rundown of the muds config file parameters...

main_port: 
    The main port number.

wiz_port:
    The wizport number. This port is not affected by the max_users option.

info_port:
    The information port number.

max_users:
    Max number of users allowed to be logged on at any given moment via the 
    main port.

start_room:
    Rooms users start off in. 

heartbeat:
    Freqency in seconds at which the event functions that run things are 
    called. 

autosave_freq:
    Freq. in seconds that everyones current stats are saved.

auto_sell_rate:
    Rate for which inventory of a user will be sold automatically if he loses 
    his connection. 0 means it won't be sold and it'll just drop into the room,
    1 means he gets full price , 2 means he gets halt price etc.

login_timeout:
    Length of time someone can idle at the login prompt before being kicked 
    off.

game_timeout:
    Length of time someone can idle in the game proper. This does not effect 
    users of wizard level or higher.

minlogin_level:
    Minimum user level that can log in. If 0 then new accounts can be created 
    too.

decay_after:
    Time taken for corpses to decay.

autofight_timeout:
    Time after which npc/user will no longer automatically attack their last 
    foe.

ignore_sigterm:
    If YES then SIGTERMs will be noted but ignored.

password_echo:
    If YES then passwords will be echoed at login.

dos_newline:
    If YES then every \n will be appended with \r for DOS and windows users.

logging_on:
    If YES then stuff is written to the system log.

start_ilr:
    If YES then users upon logging in are placed in the room they were last in
    in their last session. This is for debugging and testing purposes while the
    mudlib is being developed really as it could trap normal players in 
    certain areas.

crash_recovery:
    If YES then the mud sill attempt to recover from a crash. This isn't 
    guaranteed to work.

crash_events_halt:
    If YES then the game events will halt after a crash.

events_running:
    If YES then mud will start all the events after booting.

hostname_resolve:
    If NO then mud will not resolve IP numbers into names. This is useful if 
    the gethostbyname call is hanging for a long time.

