summaryrefslogtreecommitdiff
path: root/cmd/podman/diff.go
diff options
context:
space:
mode:
authorMatthew Heon <mheon@redhat.com>2020-05-28 14:12:19 -0400
committerMatthew Heon <mheon@redhat.com>2020-05-28 14:26:36 -0400
commite0eb6022b32f4261dbd5b78d958afc15ec2af297 (patch)
treeec86bfe91fd45d20d67619d4d9b5a3a70c033ad0 /cmd/podman/diff.go
parente704da0c520bfc1d8e0462983e8470040a2fda9d (diff)
downloadpodman-e0eb6022b32f4261dbd5b78d958afc15ec2af297.tar.gz
podman-e0eb6022b32f4261dbd5b78d958afc15ec2af297.tar.bz2
podman-e0eb6022b32f4261dbd5b78d958afc15ec2af297.zip
Ensure that signal names can be parsed on Windows
To ensure the Windows and OS X remote clients can properly parse container stop signal (when given as a name e.g. SIGTERM) and set it in SpecGen, we need access to a list of Linux signal names and the numbers they map to that is available on non-Linux OSes. Fortunately, these are ABI constants that are extremely unlikely to change, so we can just take the existing constant definitions from the library and use them. The signal numbers used here are sourced from AMD64, but should be the same for every architecture that is not Alpha, SPARC, MIPS, and PA-RISC. So `podman run --stop-signal SIGTTOU` from a Windows client to a Podman service on a SPARC host will set an incorrect stop signal, but I don't think this is a large problem. Signed-off-by: Matthew Heon <mheon@redhat.com>
Diffstat (limited to 'cmd/podman/diff.go')
0 files changed, 0 insertions, 0 deletions