Fixes for resolv.conf detection and specification#1547
Open
dvershinin wants to merge 2 commits intoalibaba:masterfrom
Open
Fixes for resolv.conf detection and specification#1547dvershinin wants to merge 2 commits intoalibaba:masterfrom
dvershinin wants to merge 2 commits intoalibaba:masterfrom
Conversation
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
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 PR fixes #1546 and also allows to unconditionally specify location of
/etc/resolv.conf, thus avoiding the file check for environments that might not yet have/etc/resolv.confcreated; as well as allowing Tengine to have its own app-specificresolv.conflocation customized.E.g.
This disables file check during built and unconditionally uses the specified filename.
Summary example:
When
--with-resolve-fileis unspecified,/etc/resolv.confis checked for existence, as prior to the change.