Don't leave launch shell waiting for CKAN to close#4517
Merged
Conversation
HebaruSan
added
Enhancement
HebaruSan
approved these changes
Feb 18, 2026
Member
HebaruSan
left a comment
HebaruSan
left a comment
There was a problem hiding this comment.
Thanks, I agree this is a "might as well" change. 🐧
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.
This is a pretty trivial change to the Debian launch script. The
/usr/bin/ckanscript currently keeps the shell open until CKAN is actually closed.execis a shell builtin that tells the shell to replace itself with the called program, preventing this. It's standardized in POSIX, and implemented by bothdashandbash, so there shouldn't be any compatibility concerns.While this won't save much memory or performance, it's such a trivial change with no downside that I can't see a reason not to do it.