connman: DHCP hostname update config#895
Open
sjugge wants to merge 1 commit intovoid-linux:masterfrom
Open
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
1 participant
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.
ConnMan default behavior is to update
/proc/sys/kernel/hostnameif it receives (a potentially stale) hostname from DHCP. If the user is not aware of this default behavior, it is mentioned deep in the man page, it can be quite the rabbit hole to troubleshoot how there is a stale hostname being set. Ask me how I know :)Given the potential impact on applications that take the hostname from
/proc/sys/kernel/hostname, and not user configured values, this can lead to bit of mess on a newly installed system. I think that warrants highlighting this behavior and configuration to prevent this behavior in the docs.