Notes |
|
|
Could we add sv_disablebannotification? |
|
|
|
For what it's worth, culling all of the banlist/whitelist notifications in my duel32 logfile with a sed script brought down the size from 229 megs to 150. |
|
|
(0006040)
|
Torr Samaho
|
2013-02-17 09:03
(edited on: 2013-02-17 09:05) |
|
Of course I can easily silence this. What should the option be called? I think we should only have one option for kinds of lists (banlist, whitelist, adminlist), so we need a neutral name, e.g. sv_quietplistparsing or something like this.
|
|
|
|
sv_iplistsnotify/sv_silentiplists. |
|
|
|
The existing "read files on a timer" cvar is sv_banfilereparsetime, so sv_banfilequietparse fits into that.
However, something that would actually be even handier would be if it still wrote to the log, but only if the number of entries in the ban/white/admin lists changed. If this would be a simple addition, please do it, otherwise simply quieting it completely would be fine. |
|
|
(0006047)
|
Dusk
|
2013-02-17 17:04
|
|
I'd rather call it "sv_quietbanfileparse" to keep it more consistent. |
|
|
(0009265)
|
Dusk
|
2014-06-13 21:17
|
|
Coming to think about this again, the entire message could just be gotten rid of IMO. |
|
|
(0018155)
|
Dusk
|
2017-08-10 14:55
|
|
Okay so note to self:
- implement an "inotify"-based system to find out when the files are changed and only reload when appropriate
- a Windows-implementation should not be so important because dedicated servers which would be interested in immediate banlist reparsing should run Linux.
- the message should be changed to only report when the file is read in and changes were found. Will need to try come up with some rewording. |
|