You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@thrift.apache.org by "Jens Geyer (Jira)" <ji...@apache.org> on 2021/03/18 23:28:00 UTC
[jira] [Updated] (THRIFT-5374) SO_LINGER should not be set on
AF_UNIX socket on WSL (portability issue)
[ https://issues.apache.org/jira/browse/THRIFT-5374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jens Geyer updated THRIFT-5374:
-------------------------------
Summary: SO_LINGER should not be set on AF_UNIX socket on WSL (portability issue) (was: SO_LINGER should not be set on AF_UNIX socket using setsockopt())
> SO_LINGER should not be set on AF_UNIX socket on WSL (portability issue)
> ------------------------------------------------------------------------
>
> Key: THRIFT-5374
> URL: https://issues.apache.org/jira/browse/THRIFT-5374
> Project: Thrift
> Issue Type: Bug
> Components: C++ - Library
> Affects Versions: 0.14.1
> Reporter: Nat Meo
> Priority: Major
>
> For an AF_UNIX socket it appears that there should not be a call to set SO_LINGER done using setsockopt(). This code appears to be doing this in places like TServerSocket where a call to _setup_sockopts() is being made for domain sockets. While this does not actually cause problems under normal Linux, it does cause problems under WSL as reported in this issue:
> https://github.com/microsoft/WSL/issues/3992
> It would be nice to fix this to allow portability for WSL and maybe just taking an extra precaution as to what options should actually be passed to domain sockets.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)