User Tools

Site Tools


server:hosting

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
server:hosting [2018/03/05 06:26]
karl reverted my "vandalism" from last time, i had been rock solid confessed, that the ports would be in the 132 range, and not 133, added mentioning of port 13325 for the watchdog
server:hosting [2019/06/16 02:33] (current)
saru [Crossfire Metaserver]
Line 53: Line 53:
  
  
-==== Server Settings ====+====== Hosting the Server ====== 
 + 
 +===== Server Settings ​=====
  
   * Edit and update the MOTD (Message of the Day) information (filename motd)   * Edit and update the MOTD (Message of the Day) information (filename motd)
Line 62: Line 64:
     * The file controls many aspects of play - permadeath or not, number of starting stat points, etc.     * The file controls many aspects of play - permadeath or not, number of starting stat points, etc.
  
-=== Players accounts ===+==== Players accounts ​====
 Player account information is stored in the /var directory (on linux this is usually /​usr/​games/​crossfire/​var/​crossfire/​). Player account information is stored in the /var directory (on linux this is usually /​usr/​games/​crossfire/​var/​crossfire/​).
    * The account file in the var directory includes account name and password information.    * The account file in the var directory includes account name and password information.
Line 69: Line 71:
    * You will need to back up each of these in order to be able to keep an archive for your players. It is generally a good idea to set up an automatic archiving script such that if something gets broken any account or player may be recovered.    * You will need to back up each of these in order to be able to keep an archive for your players. It is generally a good idea to set up an automatic archiving script such that if something gets broken any account or player may be recovered.
  
-=== DM account ===+==== DM account ​====
   * All servers should ensure that a DM account is setup and accessible   * All servers should ensure that a DM account is setup and accessible
     * DM accounts are managed via the dm_file usually located in      * DM accounts are managed via the dm_file usually located in 
Line 90: Line 92:
   help command   help command
  
-=== Crossfire Metaserver ===+==== Crossfire Metaserver ===
 + 
 +The actual location of the metaserver2 file will depend on how the server was originally installed (i.e., by source or by precompiled package, dedicated user account for running the server) so be sure to check the following possible locations:​ 
 + 
 +    /​usr/​games/​crossfire/​etc/​crossfire/​ 
 +    /​etc/​crossfire/​metaserver2 
 +    /​home/​crossfire/​etc/​crossfire/​metaserver2
  
   * If running a public server, you will most likely want to advertise your server via the metaserver (filename metaserver2)   * If running a public server, you will most likely want to advertise your server via the metaserver (filename metaserver2)
Line 104: Line 112:
  
  
-=== Guilds ===+==== Guilds ​====
  
   * Consider limiting how many guilds are initially available ​   * Consider limiting how many guilds are initially available ​
Line 112: Line 120:
  
  
-=== Crossloop ===+====== Crossloop ====== 
 One weakness of the crossfire-server binary is that any fatal error will result in your server going offline. To avoid lengthy delays whilst attending to other less important work, most server hosts choose to run the crossloop script. This handy script will restart the server if a crash occurs and create handy log files in the directory of your choosing. Crossloop is usually located within the server install directory (e.g. for linux /​usr/​games/​crossfire/​bin/​). One weakness of the crossfire-server binary is that any fatal error will result in your server going offline. To avoid lengthy delays whilst attending to other less important work, most server hosts choose to run the crossloop script. This handy script will restart the server if a crash occurs and create handy log files in the directory of your choosing. Crossloop is usually located within the server install directory (e.g. for linux /​usr/​games/​crossfire/​bin/​).
  
Line 118: Line 127:
     * crossloop.web is similar to crossloop, but also e-mails a stack trace and makes data available on the web.  To use, some variables at the top of the file need to be changed. ​ Note that make install will overwrite this file, so you will want to make a copy of it.     * crossloop.web is similar to crossloop, but also e-mails a stack trace and makes data available on the web.  To use, some variables at the top of the file need to be changed. ​ Note that make install will overwrite this file, so you will want to make a copy of it.
     * The script files assume that the core file will just be called **core**. ​ If the name is different, eg, core.//​pid//,​ crossloop will not be able to properly save the core files (but the fact that the name is fairly unique does mean it is less likely they will be overwritten)     * The script files assume that the core file will just be called **core**. ​ If the name is different, eg, core.//​pid//,​ crossloop will not be able to properly save the core files (but the fact that the name is fairly unique does mean it is less likely they will be overwritten)
- +:!: NOTE : Make sure, that the crossloop script, if it is a #!/bin/bash script, \\ 
-==Linux instructions==+has the ''​ulimit -c <​SIZE>''​ command ready; \\  
 +//​[[https://​linux.die.net/​man/​1/​bash|Bash]] ulimit// actually creates the core file by the //-c// argument, not the crossfire-server binary by itself. Until at least crossfire-server v.1.12.0 the //ulimit -c unlimited// line was not included in crossloop . \\ 
 +>bash 
 +>help ulimit 
 +>>​-c the maximum size of core files created 
 +>ulimit -a 
 +>>​core file size        (blocks, -c) 0 
 +>ulimit -c unlimited 
 +>ulimit -a 
 +>>​core file size        (blocks, -c) unlimited 
 +=====Linux instructions=====
 To start crossloop create a folder for the log files: To start crossloop create a folder for the log files:
  
Line 144: Line 163:
  
   ​   ​
-==Start crossloop on reboot==+====Start crossloop on reboot====
 Crossloop does not of itself provide a means of starting crossfire upon a system reboot. Due to power failures and other uncontrolled reboots it is generally wise to include this in your system start-up to avoid server downtime. just make sure it su's to the appropriate user before running. Crossloop does not of itself provide a means of starting crossfire upon a system reboot. Due to power failures and other uncontrolled reboots it is generally wise to include this in your system start-up to avoid server downtime. just make sure it su's to the appropriate user before running.
  
-==Linux instructions==+====More ​Linux instructions====
 FIXME explain how to create init.d entry. FIXME explain how to create init.d entry.
  
Line 155: Line 174:
   - Consider using Munin (http://​munin-monitoring.org/​) for monitoring and tacking server resources, more of a server host or administration benefit   - Consider using Munin (http://​munin-monitoring.org/​) for monitoring and tacking server resources, more of a server host or administration benefit
  
-==== Social Management ==== +====== Social Management ​====== 
-=== General Tips ===+===== General Tips =====
 If you want to attract players and build a community on your server - your server will need to be reliable, which means: If you want to attract players and build a community on your server - your server will need to be reliable, which means:
   * Available on a consistent basis   * Available on a consistent basis
Line 166: Line 185:
   * Become very, very familiar with the DM commands and how to use them   * Become very, very familiar with the DM commands and how to use them
  
-=== Banishment ===+===== Banishment ​=====
 If you intend to ban players who exploit bugs, PK other players, disrupt gameplay for others, etc. - say so in the server rules file so if/when something like this happens you can take action and avoid the long "​debate"​ afterwards (filename rules) If you intend to ban players who exploit bugs, PK other players, disrupt gameplay for others, etc. - say so in the server rules file so if/when something like this happens you can take action and avoid the long "​debate"​ afterwards (filename rules)
  
server/hosting.1520252773.txt.gz · Last modified: 2018/03/05 06:26 by karl