server:hosting
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
server:hosting [2018/03/05 07:08] – take the social management out of the linux table karl | server:hosting [2025/04/18 13:08] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 93: | Line 93: | ||
==== 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: | ||
+ | |||
+ | / | ||
+ | / | ||
+ | / | ||
* 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 135: | Line 141: | ||
To start crossloop create a folder for the log files: | To start crossloop create a folder for the log files: | ||
- | $ mkdir crossloop_dump | + | $ cd crossloop_dump/; nohup / |
- | Change directory to crossloop_dump | ||
- | $ cd crossloop_dump | + | * This does not start the crossfire server in case of OS reboot. |
- | + | * FIXME - core dumps from crashes | |
- | You can now run crossloop simply by: | + | * FIXME - using Munin (http:// |
- | + | * 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/ | ||
$ nohup / | $ nohup / |
server/hosting.1520255337.txt.gz · Last modified: (external edit)