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

Stop using signals for those faults, altogether, and move to a different notification means, like a pipe #19114

Closed
yufengwangca opened this issue Jun 2, 2022 · 1 comment · Fixed by #20560
Assignees

Comments

@yufengwangca
Copy link
Contributor

yufengwangca commented Jun 2, 2022

Problem

Currently, we reuse signal to trigger the various event on the device, this mechanism has several restrictions.

We only have very limited signal on Unix, we may run out of available signal for all events
Signal can not pass additional parameter information other than the command itself
All signals have default actions, we overwrite those default behaviors, such as Ctrl+C can not terminate the program.

Proposed Solution

Use named pipe instead of signal to trigger the event

@bzbarsky-apple
Copy link
Contributor

@yufengwangca Please put in an actual problem description. This issue is not actionable as it is...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants