On Mon, Jan 24, 2000 at 07:34:29PM -0200, Lalo Martins wrote:
> If the server kills me (sometimes happens, my ISP has reverse
> DNS misconfigured) irssi-text goes putz. It tries to reconnect,
> then tries the next server, then works for some time, then
> tries to reconnect to the old server without closing the new
> one, then it blows (usually). If I try to manually change
> servers after killed, it's even worse.
I think I _finally_ found the reason for this. When irssi finds too much lag
to server, it disconnects the server. Except it doesn't actually disconnect
the socket since it tries to wait for the server to close the connection so
the quit message gets displayed right (which is useful only when using
/quit, not when the connection is already assumed to be broken).
However I had forgotten to remove the server connection's handle from the
list of sockets to listen. So irssi still listened the server and replied to
pings etc. just as it was yet another active server, if the server ever did
come back alive after the lag disconnect. It could have crashed then too,
since the server record's memory was already been freed ..
