-- [ Picked text/plain from multipart/alternative ] I've had this problem with SourceDS for some time, after one of the updates (at this point, I'm unaware of which one it was) caused this "bug". I figured someone would have fixed it by now, but it hasn't so I suppose I should bring this to your attention. For whatever reason, when you start the SourceDS binaries (in our case, the srcds_amd binaries, havn't tried any others), it loads both banned_ip.cfg and banned_user.cfg, but banned_user.cfg gets wiped (read: becomes an empty file) on startup, but does not do the same to banned_ip.cfg. This is troublesome because when the servers refuse to start up properly (read: updates break or VALVe's authentication servers go down) we cannot issue the writeid command to the screen (a work around we added to our rebooting scripts to fix the problem), and our 4000+ user banlist gets wiped. Luckily, we had backups of our banlists after this, but it really is becoming troublesome to add all of these backups and work around to keep our banlists, when it shouldn't be deleting them on start up in the first place.
tsuehpsyde @ SourceKills.com -- _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
