Print an error when daemon pidfile dir doesn't exist #1252
Merged
Conversation
This file contains 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
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 #1251
Print an error when daemon pidfile dir doesn't exist and daemon can not start.
I've decided to add a simple dir check before the process daemonizes and redirects it's $stderr and $stdout. As an alternative we could pass
noclose=trueto Process.daemon (https://ruby-doc.org/3.3.0/Process.html#method-c-daemon) and manually redirect outputs todev/nullafter we successfully wrote to pidfile, but that leads to other issues. For example Rspec output get silenced indaemon_spec.