OHOH Wrong direction!
First execute the files to get the perm bans into the memory. After this you can write bans. In an unhappy situation (all servers are restarting at the same time) your bans get deleted. I think the solution with a symlinked banned_*.cfg is not the best to share it with all other servers. I don't know the exactly possible size, but there is a limit. Sourcebans has a workaround for this to save memory and resources. I a player enters the server, sourcebans is searching with a mysql statement in his database. If the plugin find a match, the player will be kicked and banned for 5 minutes. This saves the banned_user.cfg 2013/2/25 Rudy Bleeker <[email protected]>: > writeip // write banned ip's to banned_ip.cfg > writeid // write banned steam id's to banned_user.cfg > exec banned_ip.cfg > exec banned_user.cfg _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds
