This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: telnetlib does not send FIN when self.close() issued
Type: behavior Stage: resolved
Components: IO Versions: Python 2.6
process
Status: closed Resolution: not a bug
Dependencies: Superseder:
Assigned To: Nosy List: jackdied, jammer10000, r.david.murray
Priority: normal Keywords:

Created on 2011-01-17 21:26 by jammer10000, last changed 2022-04-11 14:57 by admin. This issue is now closed.

Messages (2)
msg126436 - (view) Author: Joe Bennett (jammer10000) Date: 2011-01-17 21:26
Hi, am running Python 2.6.5 on Unbuntu 10.04 and am seeing no FIN when a self.close() is issued... I do see a reset issued, but it looks like some of the M$ servers do not appreciate on a reset and would like a graceful teardown... I understand that an RST can be issued in the event the buffer may have data to send, I do not believe that is the case. If there is a way to verify that, please let me know...
msg126441 - (view) Author: R. David Murray (r.david.murray) * (Python committer) Date: 2011-01-17 23:29
telnetlib closes the socket, which in turn calls the OS level socket close function.  What happens after that is up to the OS tcp/ip stack, and is not under Python's control.  So if there is a bug here it isn't in Python.
History
Date User Action Args
2022-04-11 14:57:11adminsetgithub: 55138
2011-01-17 23:29:49r.david.murraysetstatus: open -> closed

nosy: + jackdied, r.david.murray
messages: + msg126441

resolution: not a bug
stage: resolved
2011-01-17 21:26:03jammer10000create