Well, I played around with some of your suggestions. I first did this in autoexec.cfg:
exec banned_ip.cfg exec banned_user.cfg writeip writeid
and that didnt fix it. The server erased the banlist on restart. So I took out the writeid, restarted, and the banlist was still there. THEN, I decided to try out my original configuration in server.cfg:
exec banned_ip.cfg writeip exec banned_user.cfg writeid
but this time took out the write* parts, and it didnt erase the banlist either. So I believe it just may be fixed.
Maarten van der Zwaart wrote:
On Mon, 03 Jan 2005 10:57:18 -0600, hondaman <[EMAIL PROTECTED]> wrote:
So, I should put this in my autoexec file? Also, is autoexec executed on every map change?
autoexec.cfg is executed when the server starts up.
exec banned_ip.cfg exec banned_user.cfg
Yes, these load the ban list into memory. (If you don't, the ban list will be empty.)
writeip writeid
These are not needed, but it does not hurt either. It will simply rewrite the ban list to file, but as the ban list has not changed, the files will not change either.
Maarten
-- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail?
_______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
_______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
