Setting up an UFO2000 server - Revision history

7Saturn: /* Using the init-script */

2015-11-17T10:38:32Z

Using the init-script

← Older revision		Revision as of 10:38, 17 November 2015
Line 118:		Line 118:

	===Using the init-script===		===Using the init-script===
	* ~~Replace~~ <code><~~username~~></code> with the username, it should be run as. Do ''not'' use ~~root for that. Better use an additional user, e.g.~~ <code>~~ufo2kuser~~</code>~~. The user doesn't need the privileges to login locally~~.		* Add the necessary additional user, dedicated to the ufo2000 service, e. g. <code>ufo2000</code>. The user doesn't need to be able to log in on that machine, it won't need to be part of additional groups for special permissions and it doesn't necessarily need a homefolder. It will only need the permissions to read and write inside the ufo2000 server folder.
			* Adapt <code>SERVERUSER = ""</code>-line with the username, it should be run by. Do ''not'' use <code>root</code> for that.
	* It should be placed in the folder <code>/etc/init.d/</code>.		* It should be placed in the folder <code>/etc/init.d/</code>.
	* It has to be executable: <code>sudo chmod 755 /etc/init.d/<scriptname></code>.		* It has to be executable: <code>sudo chmod 755 /etc/init.d/<scriptname></code>.
Line 124:		Line 125:
	* To remove it, use <code>sudo update-rc.d -f <scriptname> remove</code>.		* To remove it, use <code>sudo update-rc.d -f <scriptname> remove</code>.

	After that, the script can be used manually with <code>sudo service <scriptname> {start\|stop\|restart\|status}</code>, but usually is run by the system itself.		After that, the script can be used manually with <code>sudo service <scriptname> {start\|stop\|restart\|status}</code>, but usually is run by the system itself during bootup.

	==Ports and routers==		==Ports and routers==

7Saturn: /* Starting and stopping */

2015-11-17T10:33:35Z

Starting and stopping

← Older revision		Revision as of 10:33, 17 November 2015
Line 5:		Line 5:

	==Starting and stopping==		==Starting and stopping==
	You should have either the <code>ufo2000-srv.exe</code> (Windows) or the <code>ufo2000-srv</code> (Linux). You can either start it manually (stopping with CTRL+C) or let it be done by an init-script/the systems service-manager. For the moment, it is not recommended, to use the ''demonized''-mode, as there have been [http://openxcom.org/forum/index.php/topic,1799.msg40898.html#msg40898 reports of problems with that]. On piece of advice at this point: If you choose to run the server on a regular basis, e. g. on a root-server, ''you really should not run the server as root''. Better use an init-script, running it as a limited user. That way, it's far less dangerous, running the ufo2000-server. There are no known security issues, but the ~~problem usually~~ are the not known ~~one~~. If somebody may find any, the service run as root is ''a big security risk''. So keep that in mind, when running ufo2000 servers, or any other gaming server for that matter.		You should have either the <code>ufo2000-srv.exe</code> (Windows) or the <code>ufo2000-srv</code> (Linux). You can either start it manually (stopping with CTRL+C) or let it be done by an init-script/the systems service-manager. For the moment, it is not recommended, to use the ''demonized''-mode, as there have been [http://openxcom.org/forum/index.php/topic,1799.msg40898.html#msg40898 reports of problems with that]. On piece of advice at this point: If you choose to run the server on a regular basis, e. g. on a root-server, ''you really should not run the server as root''. Better use an init-script, running it as a limited user. That way, it's far less dangerous, running the ufo2000-server. There are no known security issues, but usually the problems are the not known ones... If somebody may find any, the service run as root is ''a big security risk''. So keep that in mind, when running ufo2000 servers, or any other gaming server for that matter.

	If you want the server to be a backup-server, '''don't forget to add it to [http://ufopaedia.org/index.php?title=Server_%28UFO2000%29#Back-up_Servers backup servers list]'''!		If you want the server to be a backup-server, '''don't forget to add it to [http://ufopaedia.org/index.php?title=Server_%28UFO2000%29#Back-up_Servers backup servers list]'''!

7Saturn: /* Example init-script */

2015-11-17T10:31:30Z

Example init-script

← Older revision		Revision as of 10:31, 17 November 2015
Line 9:		Line 9:
	If you want the server to be a backup-server, '''don't forget to add it to [http://ufopaedia.org/index.php?title=Server_%28UFO2000%29#Back-up_Servers backup servers list]'''!		If you want the server to be a backup-server, '''don't forget to add it to [http://ufopaedia.org/index.php?title=Server_%28UFO2000%29#Back-up_Servers backup servers list]'''!
	===Example init-script===		===Example init-script===
	Heres an example for an init-script for starting the server on system start with Linux:		Heres an example for an init-script for starting the server on system start with Linux via V-Init:

	#!/bin/sh		#!/bin/sh
Line 29:		Line 29:
	BINARYPATH="/path-to/ufo2000server"		BINARYPATH="/path-to/ufo2000server"
	PIDFILE="ufo2000.pid"		PIDFILE="ufo2000.pid"
			SERVERUSER = "ufo2000"
	cd "${BINARYPATH}"		cd "${BINARYPATH}"
	LIBRARYPATH="$(pwd)"		LIBRARYPATH="$(pwd)"
Line 55:		Line 56:
	if [ -x "$BINARYNAME" ]; then		if [ -x "$BINARYNAME" ]; then
	export LD_LIBRARY_PATH="${LIBRARYPATH}:${LD_LIBRARY_PATH}"		export LD_LIBRARY_PATH="${LIBRARYPATH}:${LD_LIBRARY_PATH}"
	sudo -u ~~<username>~~ "./${BINARYNAME}" ${COMMANDLINE_PARAMETERS} > /dev/null 2>&1 &		sudo -u $SERVERUSER "./${BINARYNAME}" ${COMMANDLINE_PARAMETERS} > /dev/null 2>&1 &
	echo $! > $PIDFILE		echo $! > $PIDFILE
			sudo chgrp $SERVERUSER $PIDFILE
			sudo chown $SERVERUSER $PIDFILE
	echo "UFO2000 server started."		echo "UFO2000 server started."
	else		else

7Saturn: /* Using the init-script */

2015-07-12T20:13:51Z

Using the init-script

← Older revision		Revision as of 20:13, 12 July 2015
Line 115:		Line 115:

	===Using the init-script===		===Using the init-script===
	* Replace <code><username></code> with the username, it should be run as. Do ''not'' use root for that. Better use an additional user, e.g. <code>ufo2kuser</code>. The user doesn't need the privileges to ~~log on,~~ locally.		* Replace <code><username></code> with the username, it should be run as. Do ''not'' use root for that. Better use an additional user, e.g. <code>ufo2kuser</code>. The user doesn't need the privileges to login locally.
	* It should be placed in the folder <code>/etc/init.d/</code>.		* It should be placed in the folder <code>/etc/init.d/</code>.
	* It has to be executable: <code>sudo chmod 755 /etc/init.d/<scriptname></code>.		* It has to be executable: <code>sudo chmod 755 /etc/init.d/<scriptname></code>.
Line 121:		Line 121:
	* To remove it, use <code>sudo update-rc.d -f <scriptname> remove</code>.		* To remove it, use <code>sudo update-rc.d -f <scriptname> remove</code>.

	After that, the script can be ~~uses~~ manually with <code>sudo service <scriptname> {start\|stop\|restart\|status}</code>, but usually is run by the system itself.		After that, the script can be used manually with <code>sudo service <scriptname> {start\|stop\|restart\|status}</code>, but usually is run by the system itself.

	==Ports and routers==		==Ports and routers==

7Saturn: /* Starting and stopping */

2015-06-06T19:18:35Z

Starting and stopping

← Older revision		Revision as of 19:18, 6 June 2015
Line 7:		Line 7:
	You should have either the <code>ufo2000-srv.exe</code> (Windows) or the <code>ufo2000-srv</code> (Linux). You can either start it manually (stopping with CTRL+C) or let it be done by an init-script/the systems service-manager. For the moment, it is not recommended, to use the ''demonized''-mode, as there have been [http://openxcom.org/forum/index.php/topic,1799.msg40898.html#msg40898 reports of problems with that]. On piece of advice at this point: If you choose to run the server on a regular basis, e. g. on a root-server, ''you really should not run the server as root''. Better use an init-script, running it as a limited user. That way, it's far less dangerous, running the ufo2000-server. There are no known security issues, but the problem usually are the not known one. If somebody may find any, the service run as root is ''a big security risk''. So keep that in mind, when running ufo2000 servers, or any other gaming server for that matter.		You should have either the <code>ufo2000-srv.exe</code> (Windows) or the <code>ufo2000-srv</code> (Linux). You can either start it manually (stopping with CTRL+C) or let it be done by an init-script/the systems service-manager. For the moment, it is not recommended, to use the ''demonized''-mode, as there have been [http://openxcom.org/forum/index.php/topic,1799.msg40898.html#msg40898 reports of problems with that]. On piece of advice at this point: If you choose to run the server on a regular basis, e. g. on a root-server, ''you really should not run the server as root''. Better use an init-script, running it as a limited user. That way, it's far less dangerous, running the ufo2000-server. There are no known security issues, but the problem usually are the not known one. If somebody may find any, the service run as root is ''a big security risk''. So keep that in mind, when running ufo2000 servers, or any other gaming server for that matter.

	If you want the server to be a backup-server, '''don't forget to add it to [http://ufopaedia.org/index.php?title=Server_%28UFO2000%29#Back-up_Servers ~~this~~ list]'''!		If you want the server to be a backup-server, '''don't forget to add it to [http://ufopaedia.org/index.php?title=Server_%28UFO2000%29#Back-up_Servers backup servers list]'''!
	===Example init-script===		===Example init-script===
	Heres an example for an init-script for starting the server on system start with Linux:		Heres an example for an init-script for starting the server on system start with Linux:
Line 13:		Line 13:
	#!/bin/sh		#!/bin/sh
	### BEGIN INIT INFO		### BEGIN INIT INFO
	# Provides: UFO2000 ~~Server~~ management		# Provides: UFO2000 server management
	# Required-Start:		# Required-Start:
	# Required-Stop:		# Required-Stop:

7Saturn: /* Starting and stopping */

2015-06-06T19:12:44Z

Starting and stopping

← Older revision		Revision as of 19:12, 6 June 2015
Line 5:		Line 5:

	==Starting and stopping==		==Starting and stopping==
	You should have either the <code>ufo2000-srv.exe</code> (Windows) or the <code>ufo2000-srv</code> (Linux). You can either start it manually (stopping with CTRL+C) or let it be done by an init-script/the systems service-manager. For the moment, it is not recommended, to use the ''demonized''-mode, as there have been [http://openxcom.org/forum/index.php/topic,1799.msg40898.html#msg40898 reports of problems with that]. On piece of advice at this point: If you choose to run the server on a regular basis, e. g. on a root-server, you really ''should'' not run the server as root. Better use an init-script, running it as a limited user. That way, it's far less dangerous, running the ufo2000-server. There are no known security issues, but the problem usually are the not known one. If somebody may find any, the service run as root is ''a big security risk''. So keep that in mind, when running ufo2000 servers, or any other gaming server for that matter.		You should have either the <code>ufo2000-srv.exe</code> (Windows) or the <code>ufo2000-srv</code> (Linux). You can either start it manually (stopping with CTRL+C) or let it be done by an init-script/the systems service-manager. For the moment, it is not recommended, to use the ''demonized''-mode, as there have been [http://openxcom.org/forum/index.php/topic,1799.msg40898.html#msg40898 reports of problems with that]. On piece of advice at this point: If you choose to run the server on a regular basis, e. g. on a root-server, ''you really should not run the server as root''. Better use an init-script, running it as a limited user. That way, it's far less dangerous, running the ufo2000-server. There are no known security issues, but the problem usually are the not known one. If somebody may find any, the service run as root is ''a big security risk''. So keep that in mind, when running ufo2000 servers, or any other gaming server for that matter.

	If you want the server to be a backup-server, '''don't forget to add it to [http://ufopaedia.org/index.php?title=Server_%28UFO2000%29#Back-up_Servers this list]'''!		If you want the server to be a backup-server, '''don't forget to add it to [http://ufopaedia.org/index.php?title=Server_%28UFO2000%29#Back-up_Servers this list]'''!

7Saturn: /* How to get the binary and what it brings with it */

2015-06-06T19:06:32Z

How to get the binary and what it brings with it

← Older revision		Revision as of 19:06, 6 June 2015
Line 2:		Line 2:

	==How to get the binary and what it brings with it==		==How to get the binary and what it brings with it==
	In order to run your own server, you can either use the supplied [http://prdownloads.sourceforge.net/ufo2000/ufo2000-0.9.1176-beta.exe?download precompiled ufo2000.exe] from the [http://ufo2000.sourceforge.net project page], or for linux, you will need to compile it yourself. Don't worry, the latter is no big deal. You should have a look at [[Compiling for Linux (UFO2000)#Compiling_the_server]], then. The server brings a status-page with it, a tiny webserver, that only shows, who is logged on. If you use the standard port for it, the url is http://servername:2000.		In order to run your own server, you can either use the supplied [http://prdownloads.sourceforge.net/ufo2000/ufo2000-0.9.1176-beta.exe?download precompiled ufo2000.exe] from the [http://ufo2000.sourceforge.net project page], or for linux, you will need to compile it yourself. Don't worry, the latter is no big deal. You should have a look at the [[Compiling for Linux (UFO2000)#Compiling_the_server\|compilation page]], then. The server brings a status-page with it, a tiny webserver, that only shows, who is logged on. If you use the standard port for it, the url is http://servername:2000.

	==Starting and stopping==		==Starting and stopping==

7Saturn: /* Starting and stopping */

2015-05-30T10:02:10Z

Starting and stopping

← Older revision		Revision as of 10:02, 30 May 2015
Line 7:		Line 7:
	You should have either the <code>ufo2000-srv.exe</code> (Windows) or the <code>ufo2000-srv</code> (Linux). You can either start it manually (stopping with CTRL+C) or let it be done by an init-script/the systems service-manager. For the moment, it is not recommended, to use the ''demonized''-mode, as there have been [http://openxcom.org/forum/index.php/topic,1799.msg40898.html#msg40898 reports of problems with that]. On piece of advice at this point: If you choose to run the server on a regular basis, e. g. on a root-server, you really ''should'' not run the server as root. Better use an init-script, running it as a limited user. That way, it's far less dangerous, running the ufo2000-server. There are no known security issues, but the problem usually are the not known one. If somebody may find any, the service run as root is ''a big security risk''. So keep that in mind, when running ufo2000 servers, or any other gaming server for that matter.		You should have either the <code>ufo2000-srv.exe</code> (Windows) or the <code>ufo2000-srv</code> (Linux). You can either start it manually (stopping with CTRL+C) or let it be done by an init-script/the systems service-manager. For the moment, it is not recommended, to use the ''demonized''-mode, as there have been [http://openxcom.org/forum/index.php/topic,1799.msg40898.html#msg40898 reports of problems with that]. On piece of advice at this point: If you choose to run the server on a regular basis, e. g. on a root-server, you really ''should'' not run the server as root. Better use an init-script, running it as a limited user. That way, it's far less dangerous, running the ufo2000-server. There are no known security issues, but the problem usually are the not known one. If somebody may find any, the service run as root is ''a big security risk''. So keep that in mind, when running ufo2000 servers, or any other gaming server for that matter.

	If you want the server to be a backup-server, don't forget to add it to [http://ufopaedia.org/index.php?title=Server_%28UFO2000%29#Back-up_Servers this list]!		If you want the server to be a backup-server, '''don't forget to add it to [http://ufopaedia.org/index.php?title=Server_%28UFO2000%29#Back-up_Servers this list]'''!
	===Example init-script===		===Example init-script===
	Heres an example for an init-script for starting the server on system start with Linux:		Heres an example for an init-script for starting the server on system start with Linux:

7Saturn: /* How to get the binary and what it brings with it */

2015-05-30T09:57:36Z

How to get the binary and what it brings with it

← Older revision		Revision as of 09:57, 30 May 2015
Line 2:		Line 2:

	==How to get the binary and what it brings with it==		==How to get the binary and what it brings with it==
	In order to run your own server, you can either use the supplied [http://prdownloads.sourceforge.net/ufo2000/ufo2000-0.9.1176-beta.exe?download precompiled ufo2000.exe] from the [http://ufo2000.sourceforge.net project page], or for linux, you will need to compile it yourself. Don't worry, the latter is no big deal. You should have a look at [[Compiling for Linux (UFO2000)#Compiling_the_server]], then.		In order to run your own server, you can either use the supplied [http://prdownloads.sourceforge.net/ufo2000/ufo2000-0.9.1176-beta.exe?download precompiled ufo2000.exe] from the [http://ufo2000.sourceforge.net project page], or for linux, you will need to compile it yourself. Don't worry, the latter is no big deal. You should have a look at [[Compiling for Linux (UFO2000)#Compiling_the_server]], then. The server brings a status-page with it, a tiny webserver, that only shows, who is logged on. If you use the standard port for it, the url is http://servername:2000.

	==Starting and stopping==		==Starting and stopping==

7Saturn: /* Using the init-script */

2015-05-30T09:56:22Z

Using the init-script

← Older revision		Revision as of 09:56, 30 May 2015
Line 115:		Line 115:

	===Using the init-script===		===Using the init-script===
	* Replace <code><username></code> ~~for~~ the ~~user~~, it should be run as. Do ''not'' use root for that. Better use an additional user, e.g. <code>ufo2kuser</code>. The user doesn't need the privileges to log on, locally.		* Replace <code><username></code> with the username, it should be run as. Do ''not'' use root for that. Better use an additional user, e.g. <code>ufo2kuser</code>. The user doesn't need the privileges to log on, locally.
	* It should be placed in the folder <code>/etc/init.d/</code>.		* It should be placed in the folder <code>/etc/init.d/</code>.
	* It has to be executable: <code>sudo chmod 755 /etc/init.d/<scriptname></code>.		* It has to be executable: <code>sudo chmod 755 /etc/init.d/<scriptname></code>.