Bug#673808: sauerbraten-server: Adding a sample configuration for a dedicated server

May 21st, 2012 - 10:40 am ET by apo | Report spam

This is a multi-part MIME message sent by reportbug.

MIME-Version: 1.0

Package: sauerbraten-server
Version: 0.0.20100728.dfsg+repack-3
Severity: wishlist
Tags: patch

Dear Maintainer,

i have attached a sample configuration to create a dedicated server by
using the server-init.cfg file. I have seen an example directory for
the redeclipse server package and figured it could be a good idea to
include one for sauerbraten as well.

I've also attached an example file describing the use of cron and
screen which is heavily influenced by the openarena server package in
wheezy.

I think this could help new admins with the administration of the
sauerbraten server.

Regards
Markus Koschany

Debian Release: wheezy/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages sauerbraten-server depends on:
ii libc6 2.13-32
ii libgcc1 1:4.7.0-8
ii libstdc++6 4.7.0-8
ii zlib1g 1:1.2.7.dfsg-1

sauerbraten-server recommends no packages.

Versions of packages sauerbraten-server suggests:
pn sauerbraten <none>

MIME-Version: 1.0

//// example configuration for a dedicated and public Sauerbraten server
//// copy your custom server-init.cfg to the home directory of the sauerbraten user
//// you have to create the user with adduser first, disabling shell access is recommended
//// the whole server documentation is available at http://sauerbraten.org/docs/config.html

//// optional specific IP for server to use
// serverip 123.123.123.123

//// optional specific port for server to use (default port is 28785)
//// to make your server accessible from the internet you have to open the serverport and serverport +1
//// for this example open udp port 28785 and 28786 for internet games in your firewall
//// regardless of what ports are set, port 28784 must be available for pinging servers over a LAN to work
//// for pure internet games opening port 28784 is not necessary
// serverport 28785

//// maximum number of allowed clients
maxclients 16

//// maximum number of bots a master can add - admins are unaffected by this limit
//// set to 0 to disallow bots
serverbotlimit 4

//// controls whether or not the server is intended for "public" use
//// when set to 0, allows "setmaster 1" and locked/private mastermodes (for coop-editing and such)
//// when set to 1, can only gain master by "auth" or admin, and doesn't allow locked/private mastermodes
//// when set to 2, allows "setmaster 1" but disallows private mastermode (for public coop-editing)
publicserver 2

//// description the server shows for the server browser
serverdesc "A Sauerbraten server powered by Debian"

//// password required to connect to the server
//// generally unnecessary unless you really don't want anyone connecting to your server
// serverpass "your_secret_server_password"

//// password that allows you to gain admin by "/setmaster your_secret_admin_password"
// adminpass "your_secret_admin_password"

//// controls whether or not the server reports to the masterserver 0=disabled, 1=enabled
updatemaster 1

//// optional message of the day to send to players on connect
servermotd "Welcome to Cube2:Sauerbraten"

MIME-Version: 1.0

Running the server with cron and screen

You can run the server in a screen(1) session and from a cron @reboot action.
This can be used to run multiple instances of the server; you'll need to set
a different serverport on each server after the first. It's safest to create a different user
and server-init.cfg for each server. You have to create the sauerbraten user first and you
should also disable shell access by pointing the shell to /bin/false.

To do this, you could put something like this in the sauerbraten user's
crontab:

@reboot screen -d -m -S ffa /usr/games/sauerbraten-server -q/home/sauerbraten

or in /etc/crontab or a file in /etc/cron.d:

@reboot sauerbraten screen -d -m -S ffa /usr/games/sauerbraten-server -q/home/sauerbraten

If you do that, you can access the servers' consoles by attaching a screen
session to them:

sudo -u sauerbraten screen -r ffa

To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Follow the discussion Replies

4 replies

Make a reply

Replies

#1 Martin Erik Werner

May 21st, 2012 - 11:30 am ET | Report spam

On Mon, 2012-05-21 at 16:06 +0200, apo wrote:

Package: sauerbraten-server
Version: 0.0.20100728.dfsg+repack-3
Severity: wishlist
Tags: patch

Dear Maintainer,

i have attached a sample configuration to create a dedicated server by
using the server-init.cfg file. I have seen an example directory for
the redeclipse server package and figured it could be a good idea to
include one for sauerbraten as well.

I've also attached an example file describing the use of cron and
screen which is heavily influenced by the openarena server package in
wheezy.

I think this could help new admins with the administration of the
sauerbraten server.

Regards
Markus Koschany

This looks like a neat idea, if you haven't already, you might want to
ask if upstream would be interested in including a more generic
server-init.cfg example?
(Although I wonder if we'll see any new release of sauer any time
(soon) :)

Martin Erik Werner

To UNSUBSCRIBE, email to
with a subject of "unsubscribe". Trouble? Contact

Reply to this message

#2 Markus Koschany

May 21st, 2012 - 01:40 pm ET | Report spam

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)

On 21.05.2012 17:21, Martin Erik Werner wrote:

This looks like a neat idea, if you haven't already, you might want to
ask if upstream would be interested in including a more generic
server-init.cfg example?
(Although I wonder if we'll see any new release of sauer any time
(soon) :)

I haven't asked upstream for inclusion yet. They probably consider the
documentation at [1] sufficient. I also doubt like yourself that there
will be a new sauer realease soon and i don't expect it in time for the
upcoming freeze.

The server-init.cfg is indeed really simple. There aren't a lot of
options in general and my server-init.cfg shows all documented options
in [1]. At the moment i'm not sure how i could make it more generic but
would like to hear your opinion.

I would like to see the documentation included because i think it makes
life for sauerbraten admins easier to know that they could also run the
server with a server-init.cfg. At the moment man sauerbraten-server only
describes the commandline configuration.

I also would like to see similiar documentation for all server packages
in our games section, but that's another story. :) The openarena-server
package is a good example how this should be documented.

So i think there are two options.

1. Asking upstream for inclusion which could mean the documentation is
not available in time for wheezy or at all.

2. Include it anyway and provide users with more information how to
configure the server. Maybe you could add the screen and cron text to
README.Debian and point to the server-init.cfg as an example?

I'm open for everything but in general i think the more documentation
available the better. :)

Thanks
Markus

[1] http://sauerbraten.org/docs/config.html

To UNSUBSCRIBE, email to
with a subject of "unsubscribe". Trouble? Contact

Reply to this message

#3 Martin Erik Werner

May 21st, 2012 - 02:30 pm ET | Report spam

On Mon, 2012-05-21 at 18:44 +0200, Markus Koschany wrote:

On 21.05.2012 17:21, Martin Erik Werner wrote:

> This looks like a neat idea, if you haven't already, you might want to
> ask if upstream would be interested in including a more generic
> server-init.cfg example?
> (Although I wonder if we'll see any new release of sauer any time
> (soon) :)
>

I haven't asked upstream for inclusion yet. They probably consider the
documentation at [1] sufficient. I also doubt like yourself that there
will be a new sauer realease soon and i don't expect it in time for the
upcoming freeze.

The server-init.cfg is indeed really simple. There aren't a lot of
options in general and my server-init.cfg shows all documented options
in [1]. At the moment i'm not sure how i could make it more generic but
would like to hear your opinion.

I meant "Generic" as in just s/Debian/Magic/ and tweaking the first
section to not use *nix-specific concepts.

Though obviously these need not change in a Debian version.

I would like to see the documentation included because i think it makes
life for sauerbraten admins easier to know that they could also run the
server with a server-init.cfg. At the moment man sauerbraten-server only
describes the commandline configuration.

I also would like to see similiar documentation for all server packages
in our games section, but that's another story. :) The openarena-server
package is a good example how this should be documented.

So i think there are two options.

1. Asking upstream for inclusion which could mean the documentation is
not available in time for wheezy or at all.

2. Include it anyway and provide users with more information how to
configure the server. Maybe you could add the screen and cron text to
README.Debian and point to the server-init.cfg as an example?

I meant you could do both ;)

I'm open for everything but in general i think the more documentation
available the better. :)

YES.

Thanks
Markus

[1] http://sauerbraten.org/docs/config.html

Martin Erik Werner

To UNSUBSCRIBE, email to
with a subject of "unsubscribe". Trouble? Contact

Reply to this message

#4 Markus Koschany

May 21st, 2012 - 03:40 pm ET | Report spam

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)

On 21.05.2012 20:18, Martin Erik Werner wrote:

On Mon, 2012-05-21 at 18:44 +0200, Markus Koschany wrote:

On 21.05.2012 17:21, Martin Erik Werner wrote:

This looks like a neat idea, if you haven't already, you might want to
ask if upstream would be interested in including a more generic
server-init.cfg example?
(Although I wonder if we'll see any new release of sauer any time
(soon) :)

I haven't asked upstream for inclusion yet. They probably consider the
documentation at [1] sufficient. I also doubt like yourself that there
will be a new sauer realease soon and i don't expect it in time for the
upcoming freeze.

The server-init.cfg is indeed really simple. There aren't a lot of
options in general and my server-init.cfg shows all documented options
in [1]. At the moment i'm not sure how i could make it more generic but
would like to hear your opinion.

I meant "Generic" as in just s/Debian/Magic/ and tweaking the first
section to not use *nix-specific concepts.

Though obviously these need not change in a Debian version.

I understand what you mean. But if you take a look at the
openarena-server package you'll find the word Debian in the server.cfg
file too and the documentation explains *nix specific concepts.

I personally like this approach because some packages provide an init
script others don't, some create a system user for a game and others
don't. In case of Sauerbraten you have to create a user and you have to
use a terminal multiplexer like screen to handle (multiple) servers
efficiently. In think this should be documented somehow.

I've just searched the svn repos of sauerbraten and it seems upstream
has already included a server-init.cfg. [1]

Let's take this one. It's official and generic.

So i think there are two options.

1. Asking upstream for inclusion which could mean the documentation is
not available in time for wheezy or at all.

2. Include it anyway and provide users with more information how to
configure the server. Maybe you could add the screen and cron text to
README.Debian and point to the server-init.cfg as an example?

I meant you could do both ;)

Ok, i think this issue is solved. The rest is up to you. :)

Regards
Markus

[1]
http://sauerbraten.svn.sourceforge....iew=markup

To UNSUBSCRIBE, email to
with a subject of "unsubscribe". Trouble? Contact

Follow the discussion Replies

Reply to this message

Create a new topic Replies

Make a reply

Make your own search

Bug#673808: sauerbraten-server: Adding a sample configuration for a dedicated server

Similar topics

Replies