WG: [bf1942] Info on the next beta (more features..)

Christian Lahme lahme at 4all-networks.de
Thu Jul 24 05:42:31 EDT 2003

... Sounds good... Looking forward for ob8 ... 

Kind regards - Mit freundlichen Grüßen

Christian Lahme

_ _ _

Gaja Networks GmbH
Division Gameserver
Gotenstrasse 53
65929 Frankfurt

Tel: +49 (069) 37 56 44 33
Fax: +49 (069) 37 00 26 64
Mobil: +49 (0179) 131 82 44

Mail: lahme at gaja-networks.com

Internet: www.mpx.ag
Internet: www.gaja-networks.de



The contents of the e-mail are confidential to the ordinary user of the
e-mail address to which it was addressed, and may also be privileged. If
you are not the address of this e-mail you may not copy, forward,
disclose or otherwise useit or any part of it in any form whatsoever. If
you have received this e-mail in error, please e-mail the sender by
replying to this message. Gaja Networks GmbH, Germany `` member of the
mpX technology group ``

-----Ursprüngliche Nachricht-----
Von: Andreas, Fredriksson [mailto:andreas.fredriksson at dice.se] 
Gesendet: Donnerstag, 24. Juli 2003 10:45
An: 'Steven Hartland '; 'bf1942 at icculus.org '
Betreff: RE: [bf1942] Info on the next beta (more features..)

To gain some more popularity I'm also adding a new feature for
many-server-on-one-box which attempts to reduce the lag when one of the
servers starts a new map.

Adding +priorityDaemon 1 to your command line will instruct the server
to send messages to a local root daemon that sits around changing
priorities on request. I'm including the source code of this daemon with
the next release for you to meddle with and so that you can see what it
does (it needs to run as root after all). Of course you can roll your
own daemon if you fell like it.

Basically it works like this:

You start the daemon as root, and it will bind to After
that you can start multiple bf servers with +priorityDaemon 1 and they
will have a niceness of 10 when loading, and then default back to zero
once they are ready to accept clients.

This way the loading servers shouldn't impact the playing servers as
much (even though slow disks can wreak havoc anyway).

// Andreas

-----Original Message-----
From: Steven Hartland
To: bf1942 at icculus.org
Sent: 7/24/2003 9:28 AM
Subject: Re: [bf1942] Info on the next beta

----- Original Message ----- 
From: "Andreas, Fredriksson" <andreas.fredriksson at dice.se>
> with the current implementation of +overlayPath logs are written to 
> the Logs/ subdirectory of the overlayed path. So in essence:
> $ cd /usr/local/games/bf1942-server
> $ ./start.sh +overlayPath ~/user-bf +statusMonitor 1
> will make the XML and the (fairly useless) BfLog file end up in 
> ~/bf-local/Logs/. A global log directory for all instances doesn't 
> make sense in my opinion because of the world or group write 
> permissions required to use it.
> If you really, really want it you can of course symlink the Logs 
> directory of each overlayed structure to point it at a global log 
> directory.

In our case its not a global directory but a server instance based one,
but I do know organisations which do. Your example is perfect where are
the current implementation uses "Log" we give the user access to "logs"
a subtle diff. If you have time that's great if not I'll just add a
special case to our BF1942 module which symlinks logs to Logs so no
biggy you've done the killer with +overlayPath which we will all love
you forever for :).


More information about the Bf1942 mailing list