2014-11-13 13:40:22 -05:00
|
|
|
// +build windows
|
|
|
|
|
|
|
|
package signal
|
|
|
|
|
|
|
|
import (
|
|
|
|
"syscall"
|
|
|
|
)
|
|
|
|
|
2016-09-08 14:54:01 -04:00
|
|
|
// Signals used in cli/command (no windows equivalent, use
|
2014-11-13 13:40:22 -05:00
|
|
|
// invalid signals so they don't get handled)
|
2015-07-25 04:35:07 -04:00
|
|
|
const (
|
|
|
|
SIGCHLD = syscall.Signal(0xff)
|
|
|
|
SIGWINCH = syscall.Signal(0xff)
|
2016-03-18 16:50:18 -04:00
|
|
|
SIGPIPE = syscall.Signal(0xff)
|
2015-08-04 16:51:48 -04:00
|
|
|
// DefaultStopSignal is the syscall signal used to stop a container in windows systems.
|
|
|
|
DefaultStopSignal = "15"
|
2015-07-25 04:35:07 -04:00
|
|
|
)
|
2015-10-12 17:32:59 -04:00
|
|
|
|
|
|
|
// 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,
|
|
|
|
}
|