Issue-44-SIGTERM-CONTROL: Added control over SIGTERM handling by PROCESSEXIT environment variable, set NO not to exit - #45
Open
lalitgupta-blr wants to merge 1 commit into
Open
Conversation
…ESSEXIT environment variable, set NO not to exit
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue-44-SIGTERM-CONTROL: Added control over SIGTERM handling by PROCESSEXIT environment variable (set NO not to call process.exit() in this package). If environment variable PROCESSEXIT is set to NO then this package would not exit when SIGTERM is called in the project (calling of process.exit() is skipped) where this package is included. Default behaviour remains the same (process.exit() is called). This way SIGTERM can be handled in the project where this package is included (if required by setting PROCESSEXIT environment variable).