You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 10, 2024. It is now read-only.
In order to quit the connection I have to type /quit it seems, my bouncer doesnt seem to know the client disconnected from the server and I'm missing messages once I reconnect. I'm not sure if this is the case but it seems to be so.
The text was updated successfully, but these errors were encountered:
adrien2050
changed the title
Does seem to quit the connection to the server when the client is quit through the GUI.
Doesnt seem to quit the connection to the server when the client is quit through the GUI.
Jul 5, 2023
There are two ways an IRC connection is closed, either cleanly when the client sends QUIT or "uncleanly" when the TCP connection is just closed. Often servers have long timeouts on TCP connections before the consider the client disconnected. I'm not sure a bouncer should have that, or if that is what its doing?
HexChat does try to send QUIT on exit but it won't wait forever for it to be sent and eventually just closes everything.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In order to quit the connection I have to type /quit it seems, my bouncer doesnt seem to know the client disconnected from the server and I'm missing messages once I reconnect. I'm not sure if this is the case but it seems to be so.
The text was updated successfully, but these errors were encountered: