Fixes for resolv.conf detection and specification #1547
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.conf
created; as well as allowing Tengine to have its own app-specificresolv.conf
location customized.E.g.
This disables file check during built and unconditionally uses the specified filename.
Summary example:
When
--with-resolve-file
is unspecified,/etc/resolv.conf
is checked for existence, as prior to the change.