003e3c0551
Other Unix platforms (e.g. Darwin) are also affected by the Go
runtime sending SIGURG.
This patch changes how we match the signal by just looking for the
"URG" name, which should handle any platform that has this signal
defined in the SignalMap.
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
(cherry picked from commit 05f520dd3c)
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
26 lines
863 B
Go
26 lines
863 B
Go
package signal // import "github.com/docker/docker/pkg/signal"
|
|
|
|
import (
|
|
"syscall"
|
|
)
|
|
|
|
// Signals used in cli/command (no windows equivalent, use
|
|
// invalid signals so they don't get handled)
|
|
const (
|
|
SIGCHLD = syscall.Signal(0xff)
|
|
SIGWINCH = syscall.Signal(0xff)
|
|
SIGPIPE = syscall.Signal(0xff)
|
|
// DefaultStopSignal is the syscall signal used to stop a container in windows systems.
|
|
DefaultStopSignal = "15"
|
|
)
|
|
|
|
// SignalMap is a map of "supported" signals. As per the comment in GOLang's
|
|
// ztypes_windows.go: "More invented values for signals". Windows doesn't
|
|
// really support signals in any way, shape or form that Unix does.
|
|
//
|
|
// We have these so that docker kill can be used to gracefully (TERM) and
|
|
// forcibly (KILL) terminate a container on Windows.
|
|
var SignalMap = map[string]syscall.Signal{
|
|
"KILL": syscall.SIGKILL,
|
|
"TERM": syscall.SIGTERM,
|
|
}
|