bugzilla-daemon at mindrot.org
2014-Oct-29 23:19 UTC
[Bug 1424] Cannot signal a process over a channel (rfc 4254, section 6.9)
https://bugzilla.mindrot.org/show_bug.cgi?id=1424 Iain Morgan <imorgan at nas.nasa.gov> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |imorgan at nas.nasa.gov --- Comment #36 from Iain Morgan <imorgan at nas.nasa.gov> --- Created attachment 2500 --> https://bugzilla.mindrot.org/attachment.cgi?id=2500&action=edit Update of #1699 versus 6.7p1 Updated Darren's patch. Testing limited to compiling and basic client functionality; no server testing. It looks to me like the ability to have signals "automatically passed on" is no lnnger present. That functionality is what I am really looking for: We have some users that require the ability to pass SIGINT, SIGQUIT, and SIGTERM to remote porcesses in a manner similar to what rsh supports. I like the idea of adding -O support for sending the signal. That might be more useful than the ~S mechanism. I think I would lean towards something like: -O signal INT rather than imitating kill(1)'s syntax. -- You are receiving this mail because: You are watching someone on the CC list of the bug. You are watching the assignee of the bug.
Possibly Parallel Threads
- trying to resurrect discussion about "Cannot signal a process over a channel (rfc 4254, section 6.9)"
- trying to resurrect discussion about "Cannot signal a process over a channel (rfc 4254, section 6.9)"
- [Bug 1424] Cannot signal a process over a channel (rfc 4254, section 6.9)
- [Bug 1424] Cannot signal a process over a channel (rfc 4254, section 6.9)
- [Bug 1424] Cannot signal a process over a channel (rfc 4254, section 6.9)