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.

Sign up for GitHub

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

Log when SIGKILL #172

Open
grammoboy2 opened this issue Apr 19, 2023 · 1 comment
Open

Log when SIGKILL #172

grammoboy2 opened this issue Apr 19, 2023 · 1 comment

Comments

@grammoboy2
Copy link

Does RaySession show it in the logs when SIGKILL is used as nsmd fork does already? It's useful to know if a client couldn't handle SIGTERM and maybe has issues.
@Houston4444
Copy link
Owner

No it doesn't. It could yes, although it is very rare that the daemon kills the program when the user didn't order that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@grammoboy2 @Houston4444