How can we expect fix for this as the problem has been reported,
minority of the people are having it and valve hasnt replied in any way.
All i can do now is to write bans to another file, execute it via
server.cfg but every ban set every day need to be inserted manually to
the other file
and its very time consuming.
-ics
Aaron Holmes wrote:
I had this problem on my GMod server as well. Our solution? Write a
module in Lua to save the bans elsewhere, and load them at startup. I
don't think this is possible with other steam games (no lua included)
but the only solution might be a cheap workaround until someone at valve
fixes this.
tsuehpsyde 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
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please
visit:
http://list.valvesoftware.com/mailman/listinfo/hlds_linux
