[bf1942] Info on the next beta

[Andreas, Fredriksson]

Steven,

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.

// Andreas

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

----- Original Message ----- 
From: "David Harrison" <trogspam at games.telstra.com>
> > our case, we would prefer to put the all the standard game files
> > under /usr/local/games/bf1942 which is not writeable by users and
any
> > custom mods/maps under the user's home directory along with the
> > settings and logs.
> 
> Under the new scheme, it sounds like you'll be able to do this, and
just set
> the new overlayPath thing to the home directory of the user.
> 
> Thanks Andreas for implementing this; I would call this 'required
> functionality' for a dedicated server product and it has been very
> frustrating for us that it hasn't been implemented until now - looking
> forward to the next patch.

You said it David. With this option we will be able to provide multiple
server from one install which is just not possible atm which means
that BF1942 are a nightmare to support. One thing that's potentially
missing now that I think of it is to specify a distinct log directory.
i.e. In our system we always log to the logs dir under the users config
dir. So a +logDirectory would still be good to have even if its based
below +overlayPath.

    Steve / K