-- [ Picked text/plain from multipart/alternative ] Well, the only time I've ever had that problem is when I didn't have them in the server.cfg. All my lists are still intact after all that (and believe me, I rebooted those things 5-10 times during that outage.) Have you tried switching it to the server.cfg? Maybe test this and see if it differs and let us know. Remove the writeid and just go ahead and backup your configs, then make the server.cfg run them, and remove them from the autoexec.cfg. I would test this myself, but as I don't have a server I can test this on under my personal control (I'm not going to edit a client's server) so I'll leave it up to you. I'd just like to let you know that I've never had a problem in the past (or now) with banlists being wiped unless I had forgotten to put those two configs into the server.cfg.
If it doesn't work, then I was wrong, but like I said, I've never had my banlists wiped since I added those to the server.cfg. On 12/23/06, tsuehpsyde <[EMAIL PROTECTED]> wrote: > > -- > [ Picked text/plain from multipart/alternative ] > We have had those two lines in all of our servers' autoexec.cfg files > since > day one, for over two years now. The problem isn't the lists not loading. > > The problem, which was outlined in the first post, is that after the > server > is started, banned_user.cfg becomes a blank file, even though SourceDS has > all of the bans loaded that *were* in the list when it started up. A > writeid > command needs to be issued to put the banlist back into blank > banned_user.cfg. > > On 12/23/06, Cc2iscooL <[EMAIL PROTECTED]> wrote: > > > > -- > > [ Picked text/plain from multipart/alternative ] > > Add the following to your server.cfg. > > > > exec banned_ip.cfg > > exec banned_user.cfg > > > > Enjoy. > > > > On 12/23/06, tsuehpsyde <[EMAIL PROTECTED]> wrote: > > > > > > -- > > > [ 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 > > > > > -- > > > > _______________________________________________ > > 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 > -- _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
