One of the most important parts of any software development project or server administration is documentation. In theory, people write pages and pages of this so the software or project is clearer to a person who has no experience with it, as well as making sure you know what something does when you return to it the next day.
However, there seems to be widespread neglect of documentation for game servers: outdated tutorials, dangerous advice (sometimes a disregard for basic security...), and poor explanations. In many ways you are better off figuring out the setup yourself, lest you open up your server boxen to being thoroughly rooted.
This isn't helped at all by the strange ways dedicated server binaries tend to behave. A specific example of this, for Linux HLDS: it comes with external libraries that the hlds binary must load to function. However, it makes no attempt to set the library path so you must use a workaround (setting the environment variable LD_LIBRARY_PATH to the directory hlds is located in) for it to work. If you are starting your dedicated server via init.d at system startup, there is a reason why this might be insecure if you don't pay attention when writing the script.
So in a couple of weeks (or months, or years...), I intend to set things right by correcting these mistakes and encouraging good security and basic sanity practices. Please wish me luck...
