vulpineawoo/solanum
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Fix weirdness with client_flood_burst_rate and client_flood_burst_max.

Browse source 
They are now in messages, even if client_flood_message_time is not 1.

If client_flood_message_time is not 1 (by default it is), this needs a
configuration change to maintain the same behaviour.
This commit is contained in:
Jilles Tjoelker 2011-10-04 00:57:49 +02:00
parent d182b85454
commit a75bf40dad
2 changed files with 3 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
modules/m_info.c
View file

@ -131,13 +131,13 @@ static struct InfoStruct info_table[] = {
"client_flood_burst_rate",
OUTPUT_DECIMAL,
&ConfigFileEntry.client_flood_burst_rate,
"Maximum lines per second during flood grace period, times client_flood_message_time",
"Maximum lines per second during flood grace period",
},
{
"client_flood_burst_max",
OUTPUT_DECIMAL,
&ConfigFileEntry.client_flood_burst_max,
"Number of lines to process at once before delaying, times client_flood_message_time",
"Number of lines to process at once before delaying",
},
{
"client_flood_message_num",

1
src/packet.c
View file

@ -101,6 +101,7 @@ parse_client_queued(struct Client *client_p)
allow_read = ConfigFileEntry.client_flood_burst_max;
else
allow_read = ConfigFileEntry.client_flood_burst_rate;
allow_read *= ConfigFileEntry.client_flood_message_time;
/* allow opers 4 times the amount of messages as users. why 4?
* why not. :) --fl_
*/