Spartanfrog Wrote:Well if the share one installtion, it does it automatically. You could setup a batch script possible but you can just do it by hand. In the cstrike/cfg/ folder there should be two files called banned_id (or something like that) and banned_ip. Just copy those over from the server you banned the people in, into the other server's cfg folder and overwrite that server's files.
One installation doesn't do it automatically. One server will overwrite the other.
Manually copying the files is also out of the question. Did you think what kind of hassle it will be with five servers?!
I think there are ban scripts all over the 'net for this kind of systems. You aren't the first one having multiple servers, wanting to have common ban file. I've seen script which combined two ban file every 10 minutes or so. It's something like:
cat .../server1/banned_user.cfg .../server2/banned_user.cfg |sort -u >/tmp/banned_user.cfg; /bin/cp -f /tmp/banned_user.cfg .../server1/banned_user.cfg ; /bin/cp -f /tmp/banned_user.cfg .../server2/banned_user.cfg
It's got to be done that way so the ban files don't overwrite bans in other files.
One option is also to use some kind of server plugin which stores the bans to database. Then all the servers use the common database for bans. My guess is that there are plugins for that too.
About running the servers from one install with separate cfgs or with all separate installs. I've written partial
instructions how to set up shared memory content for multi-server systems. Some feedback is already
here.
Then you can also take a look at what Nephyrin Zey has made. He's one true srcds wizard.
http://list.valvesoftware.com/mailman/private/hlds_linux/2008-June/056691.html (requires registration)
http://www.nephyrin.net/tools/nemrun/0.7/
Nephyrin Zey Wrote:Hey guys,
I've written a srcds_run replacement script called 'nemrun' along with
a helper python script 'srcupdatecheck'. This script is meant to be a
no-nonsense srcds_run replacement with some advanced features:
- Able to handle -autoupdate, including on orangebox games and setups
with ./steam in an unusual place
- Able to update servers that share a install directory:
- First server to detect an update on restart (from
map-change-restart provided by -autoupdate, or due to a manual 'quit'
or other exit/crash) will 'lock' the directory with an update.lock
file
- Lots of other features [read the rest from the mailinglist]
If I were to run several srcds installations, I would definitely use nemrun.