Torque Master Server for Linux - call for testers

I've written a Linux binary master server to be used with the Torque engines TGE/TGEA and T3D. This master server should be interesting for people running their own dedicated Linux server. It needs more testing but I want to release it soon for a price somewhat below $50.

If you think "WTF is that Torque Master Server doing?", let me try to explain it in a few simple words:

The Torque Master Server (tms) is a meeting place for Torque game servers and clients. When a Torque game server is started, it sends continuous heartbeats to the master server containing information about the game type it offers, if a password is needed to connect etc. A game client can query the master server with a game type and receives a list of matching servers. A game client can then connect to one of those returned servers.


Here's a short feature list:

• It's a native executable, it's small (< 1 MB) and fast (not run through an interpreter like Perl or Python)
• It can either be run as console application or daemon
• Options can be passed from the command line or read from a config file
• Logging to console, file and syslog (via UDP local or remote system) is possible
• The server list is stored in a SQLite database and is persistent accross restarts by default
• Timed execution of an external script or program is possible (some parameters like number of current servers and players are passed on execution)
• 32 and 64 bit version will be available
• The master was developed and tested with Ubuntu / Debian Linux but it should work with other systems, too (see the dependencies below)

To see a complete list of options, you can either download the man page or view a converted HTML version.

No blog without screenshot? Ok, here's an example I made with the timed execution option. I've used RRDtool to create some stats:




As you can see, there's not much traffic yet on my master test server. This is where I need you! Please help me with testing and point your game to the master torquemaster.shaderman.com. You can just add it to the list of master servers. If you don't know to do this, let me know.

I didn't implement the buddyList part of the protocol yet. It doesn't look too useful to me at the moment because it isn't used by any of the stock engine examples :)

Oh and if somebody is interested in the dependencies, here's the ldd list from my 64bit executable:
linux-vdso.so.1, libsqlite3.so.0, libstdc++.so.6, libm.so.6, libgcc_s.so.1, libc.so.6, libpthread.so.0, libdl.so.2, ld-linux-x86-64.so.2

I hope you like it and please don't forget to help testing :)

Thanks,

Shaderman