8db50c03e6
When receiving bans from a bursting server, if kline_delay is set to 0 (the default), rb_event_addonce will be called to schedule an event for 0 seconds in the future. While this works fine for the fallback rb_event_run function, the epoll implementation ends up scheduling a timerfd for the event in the past, which is then never executed. While fixing this, I also made rb_event_add and rb_event_addonce reject attempts to add events scheduled for 0 seconds in the future; they're instead rewritten to run 1 second in the future. |
||
|---|---|---|
| .. | ||
| include | ||
| src | ||
| .indent.pro | ||
| acinclude.m4 | ||
| aclocal.m4 | ||
| ChangeLog | ||
| config.guess | ||
| config.sub | ||
| configure | ||
| configure.ac | ||
| COPYING | ||
| CREDITS | ||
| depcomp | ||
| INSTALL | ||
| install-sh | ||
| libratbox.pc.in | ||
| ltmain.sh | ||
| Makefile.am | ||
| Makefile.in | ||
| missing | ||
| README | ||
| TODO | ||
This is libircd from ircd-ratbox. A few notes about this library: 1. Most of this code isn't anywhere near threadsafe at this point. Don't hold your breath on this either. 2. The linebuf code is designed to deal with pretty much 512 bytes per line and that is it. Anything beyond that length unless in raw mode, gets discard. For some non-irc purposes, this can be a problem, but for ircd stuff its fine. 3. The helper code when transmitting data between helpers, the same 512 byte limit applies there as we recycle the linebuf code for this.