We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hey!
Sending host-name option through DHCP is mostly ignored due to how hostname.sh works:
host-name
hostname.sh
hostname
bmc-oob
/mnt/data/hostname
Also, if there is no network connectivity on boot:
dhclient-script
In case systemd is used, this is the same logic in networkd, except the hostname seems to be set even when a hostname already is set (I didn't test).
I would suggest to not change hostname if one already exists (as per hostname command). This wouldn't solve the second case, except with systemd.
The text was updated successfully, but these errors were encountered:
+1
Sorry, something went wrong.
No branches or pull requests
Hey!
Sending
host-name
option through DHCP is mostly ignored due to howhostname.sh
works:host-name
optionhostname
commandhostname.sh
overrides the hostname with eitherbmc-oob
or with hostname stored in/mnt/data/hostname
and store the result in/mnt/data/hostname
.Also, if there is no network connectivity on boot:
hostname.sh
will sets and store it in/mnt/data/hostname
dhclient-script
won't update the hostname as one is already setIn case systemd is used, this is the same logic in networkd, except the hostname seems to be set even when a hostname already is set (I didn't test).
I would suggest to not change hostname if one already exists (as per
hostname
command). This wouldn't solve the second case, except with systemd.The text was updated successfully, but these errors were encountered: