Complete.Org: Mailing Lists: Archives: freeciv-dev: August 2000:
[Freeciv-Dev] Re: Idea: server autoread config files
Home

[Freeciv-Dev] Re: Idea: server autoread config files

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: Reinier Post <rp@xxxxxxxxxx>
Cc: FreeCiv Development <freeciv-dev@xxxxxxxxxxx>
Subject: [Freeciv-Dev] Re: Idea: server autoread config files
From: Piotr Sulecki <Piotr.Sulecki@xxxxxxxxxxxxx>
Date: Tue, 29 Aug 2000 10:32:13 +0200

Ave!

> > What do you think about having a configuration file read automatically
> > by civserver upon start?
> 
> That's what the -r option is for!

... and you have to remember the file name to read, mention it in the
scenario description, even type it all in at civserver start... Wouldn't
it be simpler for civserver to check if a file exists, and if so, read
it?

> > I'm thinking of some file (perhaps .civserverrc) which is read from
> > civserver's current directory, then (if it fails) from the home
> > directory of the user starting it, or finally from freeciv install dir.
> 
> I once did a patch to implement this but I'm not sure it's a good
> idea.  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.

What problems does civserver have with locating rulesets? Could you
explain?

PeterS.



[Prev in Thread] Current Thread [Next in Thread]