Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | imjournal fix: put ratelimiter destruction in wrong entry point | Rainer Gerhards | 2013-06-17 | 1 | -1/+1 |
| | | | | No regression, this was in recently written, never-released code. | ||||
* | implement new ratelimiting mode for imjournal | Rainer Gerhards | 2013-06-17 | 1 | -1/+15 |
| | | | | | | | | | | | | | and make imjournal use it. The new mode is needed, as imjournal uses journal's timestamp as message generation time (which otherwise is when the message entered the system, and the ratelimiter uses this as current timestamp in order to save performance). It is debatable if imjournal is doing the right thing here. But it doesn't feel totally wrong. So let's safe that debate for later ;) | ||||
* | bugfix: prevent calling tellLostCnt() twice | Tomas Heinrich | 2013-06-12 | 1 | -1/+1 |
| | |||||
* | bugfix: prevent another endless loop in the ratelimiter | Tomas Heinrich | 2013-06-12 | 1 | -1/+1 |
| | | | | | | The message that reports how many messages were lost due to ratelimiting was sent before reseting the state that led to it. If it itself got ratelimited, this could lead to an endless loop. | ||||
* | bugfix: prevent an endless loop in the ratelimiter | Tomas Heinrich | 2013-06-10 | 1 | -2/+2 |
| | | | | | | | | | If messages are being dropped because of ratelimiting, an internal message is generated to inform about this fact. This should happen only uppon the firs occurance but the counter that tracks the number of dropped messages was incremented only after sending the message. If the message itself gets ratelimited, an endless loop spins out of control. Thanks to Jerry James for notifying about this. | ||||
* | bugfix: prevent a segfault if ratelimit condition is not met | Tomas Heinrich | 2013-04-13 | 1 | -1/+13 |
| | | | | | | Move the severity-check logic inside the ratelimiter and add a new function ratelimitSetSeverity() to manipulate the treshold. Currently only utilized by the imuxsock module. | ||||
* | fix: memory leak in linux-like ratelimiter | Rainer Gerhards | 2012-10-15 | 1 | -1/+3 |
| | |||||
* | fix: we need to use loadConf to access global settings | Rainer Gerhards | 2012-10-15 | 1 | -1/+1 |
| | | | | Hint: globals need to be re-done... | ||||
* | fix: linux-like ratelimiting did not emit "final" message... | Rainer Gerhards | 2012-10-15 | 1 | -7/+17 |
| | | | | on destruction of rate limiter. | ||||
* | imptcp: support for Linux-Type ratelimiting added | Rainer Gerhards | 2012-10-15 | 1 | -5/+2 |
| | |||||
* | ratelimit: added linux-like ratelimiter type | Rainer Gerhards | 2012-10-15 | 1 | -10/+109 |
| | |||||
* | ratelimit: respect $repeatedmsgreduction setting | Rainer Gerhards | 2012-10-15 | 1 | -26/+41 |
| | |||||
* | milestone: convert imuxsock to ratelimitAddMsg() interface | Rainer Gerhards | 2012-10-15 | 1 | -3/+5 |
| | |||||
* | imudp: add input batching & ratelimiter interface | Rainer Gerhards | 2012-10-15 | 1 | -0/+1 |
| | |||||
* | ratelimiter: enable thread-safe mode & (related) API changes | Rainer Gerhards | 2012-10-15 | 1 | -58/+83 |
| | |||||
* | interface cleanup (probably not final) | Rainer Gerhards | 2012-10-15 | 1 | -1/+1 |
| | |||||
* | milestone: ratelimiter used in imptcp | Rainer Gerhards | 2012-10-15 | 1 | -12/+37 |
| | |||||
* | milestone: experimental rate limiter used in imuxsock | Rainer Gerhards | 2012-10-12 | 1 | -0/+127 |
| | |||||
* | new ratelimit: interface plumbing added | Rainer Gerhards | 2012-10-09 | 1 | -0/+56 |
no actual implementation yet done |