-
Notifications
You must be signed in to change notification settings - Fork 17.7k
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
syscall: add Pdeathsig to SysProcAttr for FreeBSD #46258
Comments
Just a note that on Linux |
Correct. |
This proposal has been added to the active column of the proposals project |
Based on the discussion above, this proposal seems like a likely accept. |
No change in consensus, so accepted. 🎉 |
Fixes golang#46258 Change-Id: I63f70e67274a9df39c757243b99b12e50a9e4784
Fixes golang#46258 Change-Id: I63f70e67274a9df39c757243b99b12e50a9e4784
To allow adding fields to ProcSysAttr which are supported on FreeBSD but not on other BSDs. For now exec_freebsd.go is an exact copy of exec_bsd.go with adjusted build tags and copyright year. For golang#46258 For golang#46259 Change-Id: I7667a0cdf1ca86ef64a147b77c06db70c5f8eb90
Fixes golang#46258 Change-Id: I63f70e67274a9df39c757243b99b12e50a9e4784
Change https://golang.org/cl/355569 mentions this issue: |
Change https://golang.org/cl/355570 mentions this issue: |
To allow adding fields to ProcSysAttr which are supported on FreeBSD but not on other BSDs. For now exec_freebsd.go is an exact copy of exec_bsd.go with adjusted build tags and copyright year. For #46258 For #46259 Change-Id: I7667a0cdf1ca86ef64a147b77c06db70c5f8eb90 Reviewed-on: https://go-review.googlesource.com/c/go/+/355569 Trust: Tobias Klauser <tobias.klauser@gmail.com> Run-TryBot: Tobias Klauser <tobias.klauser@gmail.com> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Ian Lance Taylor <iant@golang.org>
This request is to add support for Pdeathsig on FreeBSD.
FreeBSD supports requesting a signal when the parent process dies upwards from version 11.2 according to the manpages of procctl via the procctl cmd
PROC_PDEATHSIG_CTL
and querying the current configured signal viaPROC_PDEATHSIG_STATUS
The text was updated successfully, but these errors were encountered: