https://bugzilla.redhat.com/show_bug.cgi?id=1087720
Daniel Walsh changed:
What|Removed |Added
Status|ASSIGNED|CLOSED
Resolution|---
https://bugzilla.redhat.com/show_bug.cgi?id=1087720
Daniel Walsh changed:
What|Removed |Added
Assignee|dwa...@redhat.com |mh...@redhat.com
--
You are receiving
https://bugzilla.redhat.com/show_bug.cgi?id=1087720
Daniel Walsh changed:
What|Removed |Added
Assignee|jrie...@redhat.com |dwa...@redhat.com
--
You are receivin
https://bugzilla.redhat.com/show_bug.cgi?id=1087720
John Skeoch changed:
What|Removed |Added
Assignee|mh...@redhat.com|jrie...@redhat.com
--
You are receivin
https://bugzilla.redhat.com/show_bug.cgi?id=1087720
--- Comment #11 from Matthew Heon ---
Appears to be an issue with Golang proper
(https://code.google.com/p/go/issues/detail?id=4391&q=signal&colspec=ID%20Status%20Stars%20Release%20Owner%20Repo%20Summary)
Unknown when a fix will be released -
https://bugzilla.redhat.com/show_bug.cgi?id=1087720
--- Comment #10 from Matthew Heon ---
After further testing, I've managed to reproduce being unable to send signals
19, 18, and 27 to the container via --sig-proxy.
This seems to be a Golang issue. I implemented a trivial signal-catching tes
https://bugzilla.redhat.com/show_bug.cgi?id=1087720
--- Comment #8 from Matthew Heon ---
PR out: https://github.com/dotcloud/docker/pull/6544
It appears that Signal 19 is actually forwarded, also. SIGSTOP cannot be
caught, so it was actually preventing my script from printing out that it was
r
https://bugzilla.redhat.com/show_bug.cgi?id=1087720
Daniel Walsh changed:
What|Removed |Added
Status|NEW |ASSIGNED
--- Comment #7 from Daniel Wa
https://bugzilla.redhat.com/show_bug.cgi?id=1087720
--- Comment #6 from Matthew Heon ---
Signal 17, SIGCHILD, is deliberately not forwarded - upstream commit
https://github.com/dotcloud/docker/commit/440422a96346072a0a9016c4db78ff7599a702aa.
Signal 19 might actually be a Golang bug - I've cons
https://bugzilla.redhat.com/show_bug.cgi?id=1087720
--- Comment #5 from Matthew Heon ---
After further testing, I've determined that all signals are sent correctly
except 17 and 19. I'm looking into a fix for this.
--
You are receiving this mail because:
You are on the CC list for the bug.
__
https://bugzilla.redhat.com/show_bug.cgi?id=1087720
--- Comment #4 from Matthew Heon ---
With upstream Docker, signal 27 works. Signal 17, however, is still broken.
--
You are receiving this mail because:
You are on the CC list for the bug.
___
gola
https://bugzilla.redhat.com/show_bug.cgi?id=1087720
Daniel Walsh changed:
What|Removed |Added
Assignee|whe...@redhat.com |mh...@redhat.com
--
You are receiving
https://bugzilla.redhat.com/show_bug.cgi?id=1087720
Daniel Walsh changed:
What|Removed |Added
Assignee|l...@redhat.com |whe...@redhat.com
--
You are receivin
https://bugzilla.redhat.com/show_bug.cgi?id=1087720
Daniel Walsh changed:
What|Removed |Added
CC||dwa...@redhat.com
--- Comment #3 from
https://bugzilla.redhat.com/show_bug.cgi?id=1087720
Lukas Doktor changed:
What|Removed |Added
Blocks||1096276
Referenced Bugs:
https://bug
https://bugzilla.redhat.com/show_bug.cgi?id=1087720
--- Comment #2 from Lukas Doktor ---
The same bug is in upstream Docker version 0.10.0, build dc9c28f/0.10.0
--
You are receiving this mail because:
You are on the CC list for the bug.
___
golang m
https://bugzilla.redhat.com/show_bug.cgi?id=1087720
--- Comment #1 from Lukas Doktor ---
The signal 17 is also ignored.
--
You are receiving this mail because:
You are on the CC list for the bug.
___
golang mailing list
golang@lists.fedoraproject.or
17 matches
Mail list logo
