Brian Goff 9c90d3e520 Fix LXC stop signals ...

`lxc-stop` does not support sending arbitrary signals.
By default, `lxc-stop -n <id>` would send `SIGPWR`.
The lxc driver was always sending `lxc-stop -n <id> -k`, which always
sends `SIGKILL`. In this case `lxc-start` returns an exit code of `0`,
regardless of what the container actually exited with.
Because of this we must send signals directly to the process when we
can.

Also need to set quiet mode on `lxc-start` otherwise it reports an error
on `stderr` when the container exits cleanly (ie, we didn't SIGKILL it),
this error is picked up in the container logs... and isn't really an
error.

Also cleaned up some potential races for waitblocked test.

Signed-off-by: Brian Goff <cpuguy83@gmail.com>
Upstream-commit: d2c4ee37c6a4114b33a915b7dae6de70e27e7965
Component: engine

2015-05-06 11:56:48 -04:00

..

execdrivers

option to configure cgroups

2015-04-27 17:50:39 -07:00

lxc

Fix LXC stop signals

2015-05-06 11:56:48 -04:00

native

Remove unused error return

2015-05-02 15:57:57 +02:00

driver_linux.go

Feature: option for disable OOM killer

2015-05-04 21:11:29 +08:00

driver.go

Feature: option for disable OOM killer

2015-05-04 21:11:29 +08:00

pipes.go

Rename runtime/* to daemon/*

2014-04-17 14:43:01 -07:00

termconsole.go

Refactoring execdriver.Command and Container structs to support 'docker exec' and other

2014-09-01 14:30:16 -07:00

utils.go

Refactor utils/utils, fixes #11923

2015-04-14 01:37:36 +02:00