[Crossfire-wiki] [Crossfire Wiki] page changed: server:hosting

[no-reply_wiki at cross-fire.org]

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

Date        : 2016/04/18 07:03
User        : saru
Edit Summary: Added a lot more detail to the crossloop entry including how-tos for linux

@@ -97,25 +97,48 @@
      * FIXME: More information on how to do this is probably desirable
  
  
  === 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/).
  
-   * 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.
+ Please note:
      * 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. For example:
  
-   $ cd crossloop_dump/; nohup /usr/games/crossfire/bin/crossloop &
+ ==Linux instructions==
+ To start crossloop create a folder for the log files:
  
+   $ mkdir crossloop_dump
  
-     * 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 (http://munin-monitoring.org/) 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.
+ Change directory to crossloop_dump
  
+   $ cd crossloop_dump
+  
+ You can now run crossloop simply by:
+  
+   $ nohup /usr/games/crossfire/bin/crossloop &
+   
+ You can check that the server is running by running ps aux:
+ 
+   $ ps aux|grep cross
+   
+ You should see something like:
+ 
+   username      1069  0.0  0.0  13696  2360 pts/40   S+   21:53   0:00 grep --color=auto cross
+   username      32126  0.0  0.0   4476   708 pts/39   S    21:37   0:00 /bin/sh /usr/games/crossfire/bin/crossloop
+   username      32129  0.6  0.0 284264 26240 pts/39   Sl   21:37   0:05 /usr/games/crossfire/bin/crossfire-server -d -tmpdir /tmp/crossfire -log /tmp/crossfire/crossfire-2016-04-18-21:37.log
+ 
+   
+ ==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.
+ 
+ ==Linux instructions==
+ FIXME explain how to create init.d entry.
+ 
+ ==Other helpful automation considerations==
+   - 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.
+   - Consider using Munin (http://munin-monitoring.org/) for monitoring and tacking server resources, more of a server host or administration benefit
  ==== Social Management ====
  === General Tips ===
  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


IP-Address  : 59.167.121.117
Hostname    : ppp59-167-121-117.static.internode.on.net
Old Revision: http://wiki.cross-fire.org/dokuwiki/doku.php/server:hosting?rev=1411896011
New Revision: http://wiki.cross-fire.org/dokuwiki/doku.php/server:hosting

-- 
This mail was generated by DokuWiki at
http://wiki.cross-fire.org/dokuwiki/