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

Signal TERM in CS 2.1 for Linux [CORE2077] #2512

Closed
firebird-automations opened this issue Sep 12, 2008 · 7 comments
Closed

Signal TERM in CS 2.1 for Linux [CORE2077] #2512

firebird-automations opened this issue Sep 12, 2008 · 7 comments

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: @AlexPeshkoff

This bug was opriginally reported in devel by Dimitry Sibiryakov.

When classic server is used in embedded mode (is loaded into user
application's space), it handles TERM signal. But it looks like it
doesn't call other signal handlers in queue. As the result - signal
handler, set in application, isn't executed and the application continue
working.

Commits: 316641f 7d1b7b3

@firebird-automations
Copy link
Collaborator Author

Modified by: @AlexPeshkoff

assignee: Alexander Peshkov [ alexpeshkoff ]

@firebird-automations
Copy link
Collaborator Author

Commented by: @AlexPeshkoff

Now I see that it was really bad idea to invoke ISC_signal_cancel() from signal handler.
Fix does not require porting into HEAD - in HEAD code is reworked and no such problem due to it.

@firebird-automations
Copy link
Collaborator Author

Modified by: @AlexPeshkoff

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Fixed [ 1 ]

Fix Version: 2.1.2 [ 10270 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @AlexPeshkoff

Fix Version: 2.0.5 [ 10222 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

status: Resolved [ 5 ] => Closed [ 6 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pavel-zotov

QA Status: No test

@firebird-automations
Copy link
Collaborator Author

Modified by: @pavel-zotov

status: Closed [ 6 ] => Closed [ 6 ]

QA Status: No test => Cannot be tested

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment