07b6e728b5
If initialising the server context fails, but the client one succeeds, we will not only leak memory, but the error message reported for initialising the server context might not make sense, because we initialise the client context after and that could erase or change the list of queued errors. This scenario is considered rare. Nevertheless, we now initialise the client context after *successfully* initialising the server context. |
||
|---|---|---|
| .. | ||
| include | ||
| src | ||
| .indent.pro | ||
| acinclude.m4 | ||
| aclocal.m4 | ||
| ChangeLog | ||
| compile | ||
| 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.