server_cfg

[ScratchMonkey]

Using telnet to Linux 2.0.17.17 server, I added a couple of server sections. I then shut the server down (with "kill") to see what the INI looks like. I then renamed "Default" to "testserver0" in the [server_cfg] section and in the [Servers] list. Restarting the server, I get the message "Error stating daemon. Aborted". Note the misspelling. The server started up, though, or at least a bunch of processes spawned, but I could no longer log in. I killed it again, changed the name back, restarted, and I could once again log in.

[raru.kaycee]

Same with the windows server...
if you rename the [server_cfg Default] section and change it in the [server] section the server will start, but you are not able to log in. Might be a result of that the the server.db is still containing the old server_cfg name... and the server in general not knows if it should create a new server admin account (the .db and .ini files are not empty! so why should it) or rename the cfg in the .db file...
(i would be confused too )

[ScratchMonkey]

Damn, forgot the DB file. I hate binary config files. It would be better if it were plain text and the passwords in it were stored with a one-way hash, just like a *nix password file.

[BLIND]

Is there anyway to re-name the server (speaking of windows) as of now, instead of having the server_cfg Default as the name? or adding additional server to run in one admin screen (admin URL, I mean, and pick the server. If there are other posts about this, and I am missing them, please help me out by pointing me towards them.