2a8ec58c15
At the moment, if a link quits in just the right (wrong [1]) way,
the quit reason will resemble:
<-- foo (~bar@baz) has quit (Read error: (-0x0) )
This should resolve that.
[1] Peers should send a close_notify alert before abruptly shutting
down their socket. This will result in a sane quit message:
<-- foo (~bar@baz) has quit (Read error: (-0x7880) SSL -
The peer notified us that the connection is going to be closed)
[ci skip]
|
||
|---|---|---|
| .. | ||
| 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.