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
In PR #61 (e639a3f), use of the SO_REUSEPORT socket option was added. This however causes issues on Windows Subsystem for Linux (WSL), which does not (and will likely never) support SO_REUSEPORT.
Please consider adding a way to disable the use of SO_REUSEPORT, or do not fail with an exception (but rather silently) when the call to setsockopt fails with ENOPROTOOPT (at least on Linux). Unfortunately it is not possible to detect WSL at compile-time, as the userland is actually Ubuntu (or other Linux). A third option would be to perform detection at runtime (or perform some other check to see whether SO_REUSEPORT is available) but then again, that is probably more complicated than simply ignoring an ENOPROTOOPT error.
The text was updated successfully, but these errors were encountered:
In PR #61 (e639a3f), use of the SO_REUSEPORT socket option was added. This however causes issues on Windows Subsystem for Linux (WSL), which does not (and will likely never) support SO_REUSEPORT.
Strace shows the following:
By the way, SO_REUSEADDR works without issue on WSL:
Please consider adding a way to disable the use of SO_REUSEPORT, or do not fail with an exception (but rather silently) when the call to setsockopt fails with ENOPROTOOPT (at least on Linux). Unfortunately it is not possible to detect WSL at compile-time, as the userland is actually Ubuntu (or other Linux). A third option would be to perform detection at runtime (or perform some other check to see whether SO_REUSEPORT is available) but then again, that is probably more complicated than simply ignoring an ENOPROTOOPT error.
The text was updated successfully, but these errors were encountered: