dilim/containerd
1
0 Fork 0
mirror of https://github.com/containerd/containerd.git synced 2026-11-06 13:27:16 +00:00
Code Issues Packages Projects Releases Wiki Activity
17,231 Commits 31 Branches 333 Tags
bb5988d3d1da170491bbb83564976729d85c227e
Commit Graph
3 Commits
Author SHA1 Message Date
Brian Goff 899b4e3cb5 Ignore SIGURG signals in signal forwarder 
Starting with go1.14, the go runtime hijacks SIGURG but with no way to
not send to other signal handlers.

In practice, we get this signal frequently.
I found this while testing out go1.15 with ctr and multiple execs with
only `echo hello`. When the process exits quickly, if the previous
commit is not applied, you end up with an error message that it couldn't
forward SIGURG to the container (due to the process being gone).

Signed-off-by: Brian Goff <cpuguy83@gmail.com>
 2020-09-04 16:19:31 -07:00
Jess Valarezo 864b16a2cb ctr: alphabetize commands, rename signals 
Signed-off-by: Jess Valarezo <valarezo.jessica@gmail.com>
 2017-10-31 11:57:49 -07:00
Jess Valarezo ffd0d2ef58 ctr: move signals to commands package 
Signed-off-by: Jess Valarezo <valarezo.jessica@gmail.com>
 2017-10-26 16:31:23 -04:00