Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

net, syscall: enable accept4 and SOCK_CLOEXEC on dragonfly #14222

Closed
mikioh opened this issue Feb 4, 2016 · 2 comments

Comments

Projects
None yet
2 participants
@mikioh
Copy link
Contributor

commented Feb 4, 2016

DragonFly BSD 4.3 and above implements accept4 and socket creation using SOCK_CLOEXEC and SOCK_NONBLOCK flags.

@mikioh mikioh added the OS-Dragonfly label Feb 4, 2016

@mikioh mikioh added this to the Unplanned milestone Feb 4, 2016

@mikioh mikioh modified the milestones: Go1.9Maybe, Unplanned Feb 9, 2017

@gopherbot

This comment has been minimized.

Copy link

commented Apr 18, 2017

CL https://golang.org/cl/40894 mentions this issue.

@gopherbot

This comment has been minimized.

Copy link

commented Apr 18, 2017

CL https://golang.org/cl/40895 mentions this issue.

gopherbot pushed a commit that referenced this issue Apr 18, 2017

Mikio Hara
syscall: add Accept4 and SOCK_{CLOEXEC,NONBLOCK} on dragonfly
This change just picks a few constants from DragonfFly BSD 4.6 kernel
and doesn't synchronize all the existing constants with the latest
DragonFly BSD kernels.

Updates #14222.

Change-Id: Ie107a8bee1a09393b3b42b6f82489532f5d13290
Reviewed-on: https://go-review.googlesource.com/40894
Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>

@gopherbot gopherbot closed this in 33c3477 Apr 18, 2017

@golang golang locked and limited conversation to collaborators Apr 18, 2018

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
You can’t perform that action at this time.