[Freeciv-Dev] Re: Idea: server autoread config files
[Top] [All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: |
freeciv-dev@xxxxxxxxxxx (Freeciv developers) |
Subject: |
[Freeciv-Dev] Re: Idea: server autoread config files |
From: |
Reinier Post <rp@xxxxxxxxxx> |
Date: |
Tue, 29 Aug 2000 16:27:33 +0200 |
> > Unix apps suffer greatly from the 'where the hell did it get
> > *that* config again' problem and one way to solve it in this case is
> > not to read a config file by default at all. civserver has problems
> > with locating its the rulesets already.
>
> A simple solution: implement a --print-paths command line option in
> civserver.
Good idea.
> What problems does civserver have with locating rulesets? Could you
> explain?
Problem one: if you have multiple installations, it's easy to invoke
the civserver executable with incompatible rulesets by mistake.
Problem two: the existence of specified rulesets isn't checked
at the time they are specified, it's only started at game startup.
Once I witnessed the following on civserver.freeciv.org:
/set techs 0
[the user /sets a few more options]
/start
[civserver crashes, leaving everybody puzzled as to the cause]
[one by one, players reconnect]
[repeat several times]
--
Reinier
|
|