Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

os/signal: selective signal handling #1266

Closed
gjemiller opened this issue Nov 10, 2010 · 12 comments
Closed

os/signal: selective signal handling #1266

gjemiller opened this issue Nov 10, 2010 · 12 comments
Labels
FrozenDueToAge

Comments

@gjemiller
Copy link 

Current signal handling functionality in the runtime handles all signals, preventing
default behavior for SIGTSTP, SIGTTIN, and SIGTTOU.  One proximate effect of this is
that Ctrl-Z from a unix shell does not suspend any Go process that handles signals.
 
It might be generally convenient to have a way to catch only a specific 
subset of all signals, and to have some set of signals have their 
default behaviour. 

It might also occasionally be convenient to have a way to catch a 
signal and then to invoke the signal's default behaviour, or to deliver another signal
to itself or another process.
@adg
Copy link
Contributor

adg commented Nov 22, 2010

Comment 1:

Labels changed: added packagechange.

Status changed to HelpWanted.

@gopherbot
Copy link

Comment 2 by m@capitanio.org:

Currently are also all the signals SIGRTMIN - SIGRTMAX ignored, so it
is in go not possible to use them.

@alberts
Copy link
Contributor

alberts commented Mar 10, 2011

Comment 3:

http://groups.google.com/group/golang-dev/browse_thread/thread/a24470107bc3cac8

@rsc
Copy link
Contributor

rsc commented Aug 29, 2011

Comment 4:

Issue #2161 has been merged into this issue.

@rsc
Copy link
Contributor

rsc commented Oct 6, 2011

Comment 5:

Labels changed: added priority-low, removed priority-medium.

@rsc
Copy link
Contributor

rsc commented Dec 9, 2011

Comment 7:

Labels changed: added priority-someday, removed priority-low.

@rsc
Copy link
Contributor

rsc commented Dec 9, 2011

Comment 8:

Labels changed: added priority-go1.

@robpike
Copy link
Contributor

robpike commented Jan 13, 2012

Comment 9:

Owner changed to builder@golang.org.

@rsc
Copy link
Contributor

rsc commented Jan 30, 2012

Comment 11:

Labels changed: added go1-must.

@dsymonds
Copy link
Contributor

dsymonds commented Feb 1, 2012

Comment 12:

os/signal has been moved to exp/signal, and so won't be in Go 1. I'm demoting this bug's
priority.

Labels changed: added priority-later, removed priority-go1, go1-must.

Status changed to Thinking.

@rsc
Copy link
Contributor

rsc commented Feb 8, 2012

Comment 13:

Owner changed to @rsc.

Status changed to Started.

@rsc
Copy link
Contributor

rsc commented Feb 13, 2012

Comment 14:

This issue was closed by revision 35586f7.

Status changed to Fixed.

@rsc rsc mentioned this issue Dec 8, 2014
Closed
@golang golang locked and limited conversation to collaborators Jun 24, 2016
@rsc rsc removed their assignment Jun 22, 2022
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
FrozenDueToAge
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
7 participants
@dsymonds @rsc @alberts @robpike @adg @gopherbot @gjemiller