start: use SIGUSR1 for start signal#888
Closed
cyphar wants to merge 1 commit intoopencontainers:masterfrom
cyphar:start-use-sigusr1
Closed
start: use SIGUSR1 for start signal#888cyphar wants to merge 1 commit intoopencontainers:masterfrom cyphar:start-use-sigusr1
cyphar wants to merge 1 commit intoopencontainers:masterfrom
cyphar:start-use-sigusr1
Conversation
Since we don't use SIGSTOP, the choice of wait signal is arbitrary. However, Go versions before 1.6 did not support waiting for SIGCONT -- this is a problem for platforms which do not have the gc compiler (as gcc-go implements Go 1.4). Signed-off-by: Aleksa Sarai <asarai@suse.de>
Member
|
This can be closed now that we are using a pipe for this functionality. |
stefanberger
pushed a commit
to stefanberger/runc
that referenced
this pull request
Sep 8, 2017
ChangeLog: Document changes since c83b8c8
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Since we don't use SIGSTOP, the choice of wait signal is arbitrary.
However, Go versions before 1.6 did not support waiting for SIGCONT --
this is a problem for platforms which do not have the gc compiler (as
gcc-go implements Go 1.4).
This is an alternative to #886.
Signed-off-by: Aleksa Sarai asarai@suse.de