> For the complete documentation index, see [llms.txt](https://docs.linuxgsm.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.linuxgsm.com/commands/details.md). # details The `details` command allows access to various useful information about the game server. Details are gathered from configs, parameters and server queries. ## Commands ### details Standard: `./gameserver details` Short: `./gameserver dt` ### postdetails `postdetails` (using hastebin) is used to share server details, to help with support, while hiding sensitive information: Standard: `./gameserver postdetails` Short: `./gameserver pd` ## Details Provided Various relevant details are provided including: * Distro Details * Performance * Disk usage * Server Name * Server IP * Server Ports * Passwords * Config File * Backups * Server parameters ## Example output ``` Distro Details =============================================================================================================================================================== Distro: Debian 7.7 Arch: x86_64 Kernel: 2.6.32-042stab102.9 Hostname: vps86887.ovh.net tmux: tmux 1.6 GLIBC: 2.13 Performance =============================================================================================================================================================== Uptime: 0d, 17h, 36m Avg Load: 0.00, 0.02, 0.00 Mem: total used free Physical: 1.0G 1.0G 17M Swap: 128M 25M 102M Disk Usage =============================================================================================================================================================== Disk available: 5.4G Serverfiles: 1.6G Backups: 4.8M Fistful of Frags Server Details =============================================================================================================================================================== Server name: Fistful of Frags Server Server IP: 192.168.1.1:27015 RCON password: rconpassword Status: OFFLINE Service name: fof-server User: fofserver Location: /home/fofserver Config file: /home/fofserver/serverfiles/fof/cfg/fof-server.cfg Backups =============================================================================================================================================================== No. of backups: 1 Latest backup: date: Fri Jan 23 15:54:52 CET 2015 file: /home/fofserver/backups/fof-server-2015-01-23-155447.tar.gz size: 4.8M Command-line Parameters =============================================================================================================================================================== ./srcds_run -game fof -strictportbind -ip 192.168.1.1 -port 27015 +clientport 27005 +tv_port 27020 +map fof_depot +servercfgfile fof-server.cfg -maxplayers 16 Ports =============================================================================================================================================================== Change ports by editing the command-line parameters in ./fofserver. Useful port diagnostic command: netstat -atunp | grep srcds_linux DESCRIPTION DIRECTION PORT PROTOCOL > Game/RCON INBOUND 27015 tcp/udp ``` --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.linuxgsm.com/commands/details.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.