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
Hi! pkgsrc developer here. One of our users wanted to compile Caddy (a Go binary) with support for SO_REUSEPORT. I tried adding the definition to golang.org/x/sys using the standard way, which involves taking values from C header files.
I found that commit b98c37d added this support for OmniOS but put the constant into an #ifdef _KERNEL block. This seems wrong to me, since _KERNEL typically switches from user-mode to intra-kernel interfaces. Is this a bug? Or is it deliberate?
To add a little more color: The SO_REUSEPORT implementation added for LX is TCP-only, and really lacking in functionality. It only basically covers the "I want to reload haproxy without closing the socket" use case, and isn't especially robust at that. Because of its shortcomings, it was not exposed to the native system.
Hi! pkgsrc developer here. One of our users wanted to compile Caddy (a Go binary) with support for
SO_REUSEPORT
. I tried adding the definition to golang.org/x/sys using the standard way, which involves taking values from C header files.I found that commit b98c37d added this support for OmniOS but put the constant into an
#ifdef _KERNEL
block. This seems wrong to me, since_KERNEL
typically switches from user-mode to intra-kernel interfaces. Is this a bug? Or is it deliberate?/cc @pfmooney, who wrote that code.
The text was updated successfully, but these errors were encountered: