Double closing file descriptor about go-tproxy HOT 4 CLOSED

Hey Patrick,

I'm glad this library is of some help to someone. With the closing of the *os.File variables, the closing of those files doesn't affect the underlying socket, it just closes the access to the file descriptor definer. Where as calling syscall.Close on the file descriptor will instruct the kernel to close the socket.

See https://godoc.org/net#TCPConn.File

from go-tproxy.

Hi,

maybe I'm wrong but for my understanding listener.File() returns a clone(3)ed file descriptor pointing to the same socket structure. The defered file.Close() will actually close the file descriptor by invoking close(3), which has the same effect as syscall.Close(). The kernel is not going to do shutdown the socket as long as active file descriptors are attached to it. Since the listener maintains it's own fd, the socket will be kept open. (That's also how childs can inherit sockets from parents). If you really want to force the listener socket to be closed, you'll need to call listener.Close() or shutdown(3) on the clone file-descriptor. May also refer to the manpage of close(3), I think it's "more or less" clear on that.

Please correct me when I'm wrong.

Br,
Patrick

from go-tproxy.

Hey Patrick,

From some reading and going through what I implemented you are correct, I should be calling Close() on the listener instead of the cloned fd when a error occurs. Good catch!

If you want, submit a pull request with the changes and I'll approve them. Also feel free to add a contributes section in the README and add yourself to it.

Kind regards,

Liam Haworth.

from go-tproxy.

Issue resolved via PR #7

from go-tproxy.