[Crossfire-wiki] [Crossfire DokuWiki] page changed: serverhosting:hosting_a_crossfire_server

no-reply_wiki at metalforge.org no-reply_wiki at metalforge.org
Tue Jan 18 00:23:03 CST 2011


A page in your DokuWiki was added or changed. Here are the details:

Date        : 2011/01/18 00:23
User        : mwedel
Edit Summary: add information about crossloop.

@@ -51,16 +51,24 @@
      * Unfortunately, it's advised that you learn how to block (ban) networks and subnets
      * Much of this can be done in game while in DM mode (command: banish) but sometimes attacks are too widespread or not coming from player(s) from within the game
    * The ban_file (filename ban_file) can be used to ban certain IP addresses or IP ranges - this may be easier than modifying firewall rules.  Note that the check is done at connection time, so would not cause players already connected to get dropped.
    * Some of the above file changes will take effect immediately, while others require the server to restart before they take effect.
+ 
  
  
  
  ===== Technical Recommendations =====
-   * FIXME - using crossloop script or monit for automatically restarting after crashes
+   * crossloop (//prefix///bin/crossloop) can be used to automatically restart crossfire if the program crashes.
+     * It stores the core files in the current directory, so this should be run from the directory you want to store those core files.
+     * 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)
+     * To start, do 'cd somedir; nohup /path/to/crossloop &' - note that different shells may nohup by default - somedir is where you want all the core files to be.
+     * This does not start the crossfire server in case of OS reboot.  Crossfire does not include a script that does this, but generally, it is not hard to write one - just make sure it su's to the appropriate user before running.
    * FIXME - core dumps from crashes 
    * FIXME - using munin for monitoring and tacking server resources, more of a server host or administration benefit
    * Have an automated and remote backup of player files and unique map files in case of hardware failure, data corruption or accident
+     * All crossfire files are text, so generally easy to back up and restore
+     * Since files are text, one can even attempt to repair damaged/corrupted files.
  
  
  ===== Other Recommendations =====
  


IP-Address  : 173.228.106.246
Old Revision: http://wiki.metalforge.net/doku.php/serverhosting:hosting_a_crossfire_server?rev=1295330810
New Revision: http://wiki.metalforge.net/doku.php/serverhosting:hosting_a_crossfire_server

-- 
This mail was generated by DokuWiki at
http://wiki.metalforge.net/




More information about the crossfire-wiki mailing list