[opensuse] 13.1 - 'hostname' returns fqdn instead of just hostname - install put fqdn in HOSTNAME?
Brain-trust, Here is a curiosity in 13.1. After install, the hostname command returned the fully qualified domain name instead of properly returning the hostname alone. Eg: $ hostname alchemy.3111skyline.com $ hostname -f alchemy.3111skyline.com This caused problems in some application that are expecting only the hostname part. Picking through the usual list of suspects, it turned out that /etc/HOSTNAME was the guilty party. It contained: # cat HOSTNAME alchemy.3111skyline.com That was odd, in the past, /etc/HOSTNAME generally included only the hostname part and not the dnsdomainname as well. Fixing /etc/HOSTNAME fixed the problem. Has anyone else noticed this? If this can be confirmed, I'll file the bug report, but there is also the possibility I entered the full hostname during install when it called for only the hostname part. I guess in that instance I should still file a bug report because the installer should be smart enough to validate the input. What says the list? -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2014-07-18 03:16 (GMT-0500) David C. Rankin composed:
Brain-trust,
Here is a curiosity in 13.1. After install, the hostname command returned the fully qualified domain name instead of properly returning the hostname alone. Eg:
$ hostname alchemy.3111skyline.com
$ hostname -f alchemy.3111skyline.com
This caused problems in some application that are expecting only the hostname part. Picking through the usual list of suspects, it turned out that /etc/HOSTNAME was the guilty party. It contained:
# cat HOSTNAME alchemy.3111skyline.com
That was odd, in the past, /etc/HOSTNAME generally included only the hostname part and not the dnsdomainname as well. Fixing /etc/HOSTNAME fixed the problem.
Has anyone else noticed this? If this can be confirmed, I'll file the bug report, but there is also the possibility I entered the full hostname during install when it called for only the hostname part. I guess in that instance I should still file a bug report because the installer should be smart enough to validate the input. What says the list?
Before filing, take a look at these: https://bugzilla.novell.com/show_bug.cgi?id=872264 https://bugzilla.novell.com/show_bug.cgi?id=883999 https://bugzilla.novell.com/show_bug.cgi?id=887039 -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2014-07-18 03:16 (GMT-0500) David C. Rankin composed:
# cat HOSTNAME alchemy.3111skyline.com
That was odd, in the past, /etc/HOSTNAME generally included only the hostname part and not the dnsdomainname as well. Fixing /etc/HOSTNAME fixed the problem.
Has anyone else noticed this?
Hi Yes. It only matters if you have DNS critical stuff like Kerberos because the search domains in /etc/resolv.conf are appended to the contents of /etc/HOSTNAME. So for us at least /etc/HOSTNAME _must_ contain the short hostname. e.g. in your case, your box in DNS critical situations would be: alchemy.3111skyline.com.3111skyline.com I don't think it's a bug because I don't think anyone has the definitive answer. Ubuntu hits it as close as we've ever seen, 'etc/hostname This file should only contain domain name and not the full FQDN'. But that's /etc/hostname. We don't have that file on 13.1;) Aything which returns: hostname -s hostname -f and hostname -d correctly will get you there. Then check that the A records are correct with dig. HTH L x -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Friday 18 Jul 2014 03:16:39 David C. Rankin wrote:
Brain-trust,
Here is a curiosity in 13.1. After install, the hostname command returned the fully qualified domain name instead of properly returning the hostname alone. Eg:
$ hostname alchemy.3111skyline.com
$ hostname -f alchemy.3111skyline.com
This caused problems in some application that are expecting only the hostname part. Picking through the usual list of suspects, it turned out that /etc/HOSTNAME was the guilty party. It contained:
# cat HOSTNAME alchemy.3111skyline.com
That was odd, in the past, /etc/HOSTNAME generally included only the hostname part and not the dnsdomainname as well. Fixing /etc/HOSTNAME fixed the problem.
Has anyone else noticed this? If this can be confirmed, I'll file the bug report, but there is also the possibility I entered the full hostname during install when it called for only the hostname part. I guess in that instance I should still file a bug report because the installer should be smart enough to validate the input. What says the list?
Hi David, I just had a look at an opensuse 13.1 VM I have installed in a test rig (this one runs kolab which requires correct response from the hostname commands) and I do not see what you are seeing. Here is the output from this VM andrew@kolab:~> cat /etc/HOSTNAME kolab.test.rig andrew@kolab:~> hostname kolab andrew@kolab:~> hostname -s kolab andrew@kolab:~> hostname -f kolab.test.rig andrew@kolab:~> cat /etc/hosts # # hosts This file describes a number of hostname-to-address # mappings for the TCP/IP subsystem. It is mostly # used at boot time, when no name servers are running. # On small systems, this file can be used instead of a # "named" name server. # Syntax: # # IP-Address Full-Qualified-Hostname Short-Hostname # 127.0.0.1 localhost # special IPv6 addresses ::1 localhost ipv6-localhost ipv6-loopback fe00::0 ipv6-localnet ff00::0 ipv6-mcastprefix ff02::1 ipv6-allnodes ff02::2 ipv6-allrouters ff02::3 ipv6-allhosts 192.168.200.210 kolab.test.rig kolab 192.168.200.210 kolab.test.rig kolab Do you have the hosts entry? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 07/18/2014 08:21 AM, apc@abcj.demon.co.uk pecked at the keyboard and wrote:
On Friday 18 Jul 2014 03:16:39 David C. Rankin wrote:
Brain-trust,
Here is a curiosity in 13.1. After install, the hostname command returned the fully qualified domain name instead of properly returning the hostname alone. Eg:
$ hostname alchemy.3111skyline.com
$ hostname -f alchemy.3111skyline.com
This caused problems in some application that are expecting only the hostname part. Picking through the usual list of suspects, it turned out that /etc/HOSTNAME was the guilty party. It contained:
# cat HOSTNAME alchemy.3111skyline.com
That was odd, in the past, /etc/HOSTNAME generally included only the hostname part and not the dnsdomainname as well. Fixing /etc/HOSTNAME fixed the problem.
Has anyone else noticed this? If this can be confirmed, I'll file the bug report, but there is also the possibility I entered the full hostname during install when it called for only the hostname part. I guess in that instance I should still file a bug report because the installer should be smart enough to validate the input. What says the list?
Hi David,
I just had a look at an opensuse 13.1 VM I have installed in a test rig (this one runs kolab which requires correct response from the hostname commands) and I do not see what you are seeing. Here is the output from this VM andrew@kolab:~> cat /etc/HOSTNAME kolab.test.rig andrew@kolab:~> hostname kolab andrew@kolab:~> hostname -s kolab andrew@kolab:~> hostname -f kolab.test.rig
You may want to check your alias' to see if something is set different for hostname. -- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Friday 18 Jul 2014 09:31:53 Ken Schneider - openSUSE wrote:
On 07/18/2014 08:21 AM, apc@abcj.demon.co.uk pecked at the keyboard and
wrote:
On Friday 18 Jul 2014 03:16:39 David C. Rankin wrote:
Brain-trust,
Here is a curiosity in 13.1. After install, the hostname command returned
the fully qualified domain name instead of properly returning the hostname alone. Eg:
$ hostname alchemy.3111skyline.com
$ hostname -f alchemy.3111skyline.com
This caused problems in some application that are expecting only the
hostname part. Picking through the usual list of suspects, it turned out
that /etc/HOSTNAME was the guilty party. It contained: # cat HOSTNAME
alchemy.3111skyline.com
That was odd, in the past, /etc/HOSTNAME generally included only the
hostname part and not the dnsdomainname as well. Fixing /etc/HOSTNAME fixed the problem.
Has anyone else noticed this? If this can be confirmed, I'll file the bug
report, but there is also the possibility I entered the full hostname during install when it called for only the hostname part. I guess in that instance I should still file a bug report because the installer should be smart enough to validate the input. What says the list?
Hi David,
I just had a look at an opensuse 13.1 VM I have installed in a test rig (this one runs kolab which requires correct response from the hostname commands) and I do not see what you are seeing. Here is the output from this VM andrew@kolab:~> cat /etc/HOSTNAME kolab.test.rig andrew@kolab:~> hostname kolab andrew@kolab:~> hostname -s kolab andrew@kolab:~> hostname -f kolab.test.rig
You may want to check your alias' to see if something is set different for hostname.
hostname isn't a link and is found in /bin no shell alias either. Interestingly I have factory VM set up on the same virtual network which has linux.site in HOSTNAME but "hostname -f" reports linux.test.rig which shows that the domain part has come from the dhcp (dns-masq on the kvm host). The kolab vm is set up with static IP I do not know if that helps David A -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 07/18/2014 09:31 AM, Ken Schneider - openSUSE pecked at the keyboard and wrote:
On 07/18/2014 08:21 AM, apc@abcj.demon.co.uk pecked at the keyboard and wrote:
On Friday 18 Jul 2014 03:16:39 David C. Rankin wrote:
Brain-trust,
Here is a curiosity in 13.1. After install, the hostname command returned the fully qualified domain name instead of properly returning the hostname alone. Eg:
$ hostname alchemy.3111skyline.com
$ hostname -f alchemy.3111skyline.com
This caused problems in some application that are expecting only the hostname part. Picking through the usual list of suspects, it turned out that /etc/HOSTNAME was the guilty party. It contained:
# cat HOSTNAME alchemy.3111skyline.com
That was odd, in the past, /etc/HOSTNAME generally included only the hostname part and not the dnsdomainname as well. Fixing /etc/HOSTNAME fixed the problem.
Has anyone else noticed this? If this can be confirmed, I'll file the bug report, but there is also the possibility I entered the full hostname during install when it called for only the hostname part. I guess in that instance I should still file a bug report because the installer should be smart enough to validate the input. What says the list?
Hi David,
I just had a look at an opensuse 13.1 VM I have installed in a test rig (this one runs kolab which requires correct response from the hostname commands) and I do not see what you are seeing. Here is the output from this VM andrew@kolab:~> cat /etc/HOSTNAME kolab.test.rig andrew@kolab:~> hostname kolab andrew@kolab:~> hostname -s kolab andrew@kolab:~> hostname -f kolab.test.rig
You may want to check your alias' to see if something is set different for hostname.
That's not it as I have the same results as David. Sorry for the noise. -- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 07/18/2014 07:21 AM, apc@abcj.demon.co.uk wrote:
Hi David,
I just had a look at an opensuse 13.1 VM I have installed in a test rig (this one runs kolab which requires correct response from the hostname commands) and I do not see what you are seeing. Here is the output from this VM andrew@kolab:~> cat /etc/HOSTNAME kolab.test.rig andrew@kolab:~> hostname kolab andrew@kolab:~> hostname -s kolab andrew@kolab:~> hostname -f kolab.test.rig <snip> # # IP-Address Full-Qualified-Hostname Short-Hostname #
127.0.0.1 localhost
# special IPv6 addresses ::1 localhost ipv6-localhost ipv6-loopback
fe00::0 ipv6-localnet
ff00::0 ipv6-mcastprefix ff02::1 ipv6-allnodes ff02::2 ipv6-allrouters ff02::3 ipv6-allhosts 192.168.200.210 kolab.test.rig kolab 192.168.200.210 kolab.test.rig kolab
Do you have the hosts entry?
I generally do not include the alias to my specific IP in /etc/hosts. I do alias localhost:
# IP-Address Full-Qualified-Hostname Short-Hostname
127.0.0.1 alchemy.3111skyline.com localhost alchemy The issue in my case was /etc/HOSTNAME was filled with 'alchemy.3111skyline.com' on install instead of just 'alchemy' as most other suse/openSuSE installs have done since? 7.0 ftp install over dial-up? Simply fixing /etc/HOSTNAME solved the issue, the real problem is why did the fqdn end up in /etc/HOSTNAME in the first place... -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
per my upstream, this all arises, or arose, from mismatch between 'legacy' hostname and systemd management read man hostname man hostnamectl http://www.freedesktop.org/software/systemd/man/hostnamectl.html for correct/consistent hostname setup with OS 13.1, I now do MY_FQDN_HOSTNAME="mydesk.domain.com" ln -sf /etc/HOSTNAME /etc/hostname echo ${MY_FQDN_HOSTNAME} > /etc/hostnameX hostname -F /etc/HOSTNAME hostnamectl --static --transient --pretty set-hostname ${MY_FQDN_HOSTNAME} checking hostnamectl status Static hostname: mydesk.domain.com Transient hostname: mydesk Icon name: computer-desktop Chassis: desktop Machine ID: 192...28f Boot ID: 728...d04 Operating System: openSUSE 13.1 (Bottle) (x86_64) CPE OS Name: cpe:/o:opensuse:opensuse:13.1 Kernel: Linux 3.15.5-1.g01d2774-desktop Architecture: x86_64 hostname mydesk hostname -s mydesk hostname -f mydesk.domain.com is, now, consistent. ime, makes both my desktop apps and my servers happy. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
typo above - echo ${MY_FQDN_HOSTNAME} > /etc/hostnameX + echo ${MY_FQDN_HOSTNAME} > /etc/hostname -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 07/18/2014 04:50 PM, grantksupport@operamail.com wrote:
per my upstream, this all arises, or arose, from mismatch between 'legacy' hostname and systemd management
read
man hostname man hostnamectl http://www.freedesktop.org/software/systemd/man/hostnamectl.html
for correct/consistent hostname setup with OS 13.1, I now do
MY_FQDN_HOSTNAME="mydesk.domain.com"
ln -sf /etc/HOSTNAME /etc/hostname echo ${MY_FQDN_HOSTNAME} > /etc/hostnameX hostname -F /etc/HOSTNAME
hostnamectl --static --transient --pretty set-hostname ${MY_FQDN_HOSTNAME}
checking
hostnamectl status Static hostname: mydesk.domain.com Transient hostname: mydesk Icon name: computer-desktop Chassis: desktop Machine ID: 192...28f Boot ID: 728...d04 Operating System: openSUSE 13.1 (Bottle) (x86_64) CPE OS Name: cpe:/o:opensuse:opensuse:13.1 Kernel: Linux 3.15.5-1.g01d2774-desktop Architecture: x86_64
hostname mydesk
hostname -s mydesk
hostname -f mydesk.domain.com
is, now, consistent. ime, makes both my desktop apps and my servers happy.
I think simply correcting /etc/HOSTNAME on openSuSE 13.1 took care of all issues: 16:13 alchemy:~> hostnamectl status Static hostname: alchemy Icon name: computer-laptop Chassis: laptop Machine ID: b918ea6883fbabffd9bae79653c1dd82 Boot ID: a586eea49d304ea5bca3dae7502ea331 Operating System: openSUSE 13.1 (Bottle) (x86_64) CPE OS Name: cpe:/o:opensuse:opensuse:13.1 Kernel: Linux 3.11.10-17-desktop Architecture: x86_64 17:17 alchemy:~> hostname alchemy 17:18 alchemy:~> hostname -s alchemy 17:19 alchemy:~> hostname -f alchemy.3111skyline.com Comparing against Archlinux (which makes no use of /etc/HOSTNAME) the operation is the same. The Arch box is a full-server and has no resolution problems: 16:13 phoinix:.../pkg/x86_64> hostnamectl status Static hostname: phoinix Icon name: computer-desktop Chassis: desktop Machine ID: 8d32bcc3152b4a1f87c4d71f948f93fb Boot ID: 85795ece61404ea58409cec3187d3003 Operating System: Arch Linux Kernel: Linux 3.14.1-1-ARCH Architecture: x86-64 17:18 phoinix:.../pkg/x86_64> hostname phoinix 17:18 phoinix:.../pkg/x86_64> hostname -s phoinix 17:18 phoinix:.../pkg/x86_64> hostname -f phoinix.rlfpllc.com I haven't drilled-down on how systemd manages this issue, but it appears all is working correctly now. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
note a difference mine: hostnamectl status Static hostname: mydesk.domain.com Transient hostname: mydesk ... yours hostnamectl status Static hostname: alchemy ... FQDN vs Short, for 'Static hostname' These may have different/unintended results. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* David C. Rankin <drankinatty@suddenlinkmail.com> [07-18-14 18:22]: [...]
I think simply correcting /etc/HOSTNAME on openSuSE 13.1 took care of all issues:
16:13 alchemy:~> hostnamectl status Static hostname: alchemy Icon name: computer-laptop Chassis: laptop Machine ID: b918ea6883fbabffd9bae79653c1dd82 Boot ID: a586eea49d304ea5bca3dae7502ea331 Operating System: openSUSE 13.1 (Bottle) (x86_64) CPE OS Name: cpe:/o:opensuse:opensuse:13.1 Kernel: Linux 3.11.10-17-desktop Architecture: x86_64 17:17 alchemy:~> hostname alchemy 17:18 alchemy:~> hostname -s alchemy 17:19 alchemy:~> hostname -f alchemy.3111skyline.com
Comparing against Archlinux (which makes no use of /etc/HOSTNAME) the operation is the same. The Arch box is a full-server and has no resolution problems:
16:13 phoinix:.../pkg/x86_64> hostnamectl status Static hostname: phoinix Icon name: computer-desktop Chassis: desktop Machine ID: 8d32bcc3152b4a1f87c4d71f948f93fb Boot ID: 85795ece61404ea58409cec3187d3003 Operating System: Arch Linux Kernel: Linux 3.14.1-1-ARCH Architecture: x86-64 17:18 phoinix:.../pkg/x86_64> hostname phoinix 17:18 phoinix:.../pkg/x86_64> hostname -s phoinix 17:18 phoinix:.../pkg/x86_64> hostname -f phoinix.rlfpllc.com
I haven't drilled-down on how systemd manages this issue, but it appears all is working correctly now.
I don't know that changing /etc/HOSTNAME is really necessary. On my six local openSUSE boxes, I have: cat /etc/HOSTNAME Crash.wahoo.no-ip.org (all boxes exhibit similar results) # hostnamectl status Static hostname: Crash.wahoo.no-ip.org Transient hostname: Crash Icon name: computer-desktop Chassis: desktop Machine ID: 8256ba7d0e3911cd735ec8c4000004e6 Boot ID: b33c7360c07248ffa4d38b414a062753 Operating System: openSUSE 13.1 (Bottle) (x86_64) CPE OS Name: cpe:/o:opensuse:opensuse:13.1 Kernel: Linux 3.15.5-39.g01d2774-desktop Architecture: x86_64 # hostname Crash I have yet to experienced noticable problems with this condition. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Fri, 2014-07-18 at 18:34 -0400, Patrick Shanahan wrote:
* David C. Rankin <drankinatty@suddenlinkmail.com> [07-18-14 18:22]:
[...]
I think simply correcting /etc/HOSTNAME on openSuSE 13.1 took care of all issues:
16:13 alchemy:~> hostnamectl status Static hostname: alchemy Icon name: computer-laptop Chassis: laptop Machine ID: b918ea6883fbabffd9bae79653c1dd82 Boot ID: a586eea49d304ea5bca3dae7502ea331 Operating System: openSUSE 13.1 (Bottle) (x86_64) CPE OS Name: cpe:/o:opensuse:opensuse:13.1 Kernel: Linux 3.11.10-17-desktop Architecture: x86_64 17:17 alchemy:~> hostname alchemy 17:18 alchemy:~> hostname -s alchemy 17:19 alchemy:~> hostname -f alchemy.3111skyline.com
Comparing against Archlinux (which makes no use of /etc/HOSTNAME) the operation is the same. The Arch box is a full-server and has no resolution problems:
16:13 phoinix:.../pkg/x86_64> hostnamectl status Static hostname: phoinix Icon name: computer-desktop Chassis: desktop Machine ID: 8d32bcc3152b4a1f87c4d71f948f93fb Boot ID: 85795ece61404ea58409cec3187d3003 Operating System: Arch Linux Kernel: Linux 3.14.1-1-ARCH Architecture: x86-64 17:18 phoinix:.../pkg/x86_64> hostname phoinix 17:18 phoinix:.../pkg/x86_64> hostname -s phoinix 17:18 phoinix:.../pkg/x86_64> hostname -f phoinix.rlfpllc.com
I haven't drilled-down on how systemd manages this issue, but it appears all is working correctly now.
I don't know that changing /etc/HOSTNAME is really necessary. On my six local openSUSE boxes, I have:
cat /etc/HOSTNAME Crash.wahoo.no-ip.org
(all boxes exhibit similar results)
# hostnamectl status Static hostname: Crash.wahoo.no-ip.org Transient hostname: Crash Icon name: computer-desktop Chassis: desktop Machine ID: 8256ba7d0e3911cd735ec8c4000004e6 Boot ID: b33c7360c07248ffa4d38b414a062753 Operating System: openSUSE 13.1 (Bottle) (x86_64) CPE OS Name: cpe:/o:opensuse:opensuse:13.1 Kernel: Linux 3.15.5-39.g01d2774-desktop Architecture: x86_64
# hostname Crash
Are any of you working on networks where this matters? The last configuration where six machines have the same hostname in the same domain is puzzling. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* lynn <lynn@steve-ss.com> [07-19-14 01:32]:
On Fri, 2014-07-18 at 18:34 -0400, Patrick Shanahan wrote:
* David C. Rankin <drankinatty@suddenlinkmail.com> [07-18-14 18:22]:
[...]
I think simply correcting /etc/HOSTNAME on openSuSE 13.1 took care of all issues:
16:13 alchemy:~> hostnamectl status Static hostname: alchemy Icon name: computer-laptop Chassis: laptop Machine ID: b918ea6883fbabffd9bae79653c1dd82 Boot ID: a586eea49d304ea5bca3dae7502ea331 Operating System: openSUSE 13.1 (Bottle) (x86_64) CPE OS Name: cpe:/o:opensuse:opensuse:13.1 Kernel: Linux 3.11.10-17-desktop Architecture: x86_64 17:17 alchemy:~> hostname alchemy 17:18 alchemy:~> hostname -s alchemy 17:19 alchemy:~> hostname -f alchemy.3111skyline.com
Comparing against Archlinux (which makes no use of /etc/HOSTNAME) the operation is the same. The Arch box is a full-server and has no resolution problems:
16:13 phoinix:.../pkg/x86_64> hostnamectl status Static hostname: phoinix Icon name: computer-desktop Chassis: desktop Machine ID: 8d32bcc3152b4a1f87c4d71f948f93fb Boot ID: 85795ece61404ea58409cec3187d3003 Operating System: Arch Linux Kernel: Linux 3.14.1-1-ARCH Architecture: x86-64 17:18 phoinix:.../pkg/x86_64> hostname phoinix 17:18 phoinix:.../pkg/x86_64> hostname -s phoinix 17:18 phoinix:.../pkg/x86_64> hostname -f phoinix.rlfpllc.com
I haven't drilled-down on how systemd manages this issue, but it appears all is working correctly now.
I don't know that changing /etc/HOSTNAME is really necessary. On my six local openSUSE boxes, I have:
cat /etc/HOSTNAME Crash.wahoo.no-ip.org
(all boxes exhibit similar results)
# hostnamectl status Static hostname: Crash.wahoo.no-ip.org Transient hostname: Crash Icon name: computer-desktop Chassis: desktop Machine ID: 8256ba7d0e3911cd735ec8c4000004e6 Boot ID: b33c7360c07248ffa4d38b414a062753 Operating System: openSUSE 13.1 (Bottle) (x86_64) CPE OS Name: cpe:/o:opensuse:opensuse:13.1 Kernel: Linux 3.15.5-39.g01d2774-desktop Architecture: x86_64
# hostname Crash
Are any of you working on networks where this matters? The last configuration where six machines have the same hostname in the same domain is puzzling.
Not puzzling at all, re:
cat /etc/HOSTNAME Crash.wahoo.no-ip.org
(all boxes exhibit similar results)
all have hostnames *******.wahoo.no-ip.org :^) -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Patrick Shanahan wrote:
* David C. Rankin <drankinatty@suddenlinkmail.com> [07-18-14 18:22]:
Are any of you working on networks where this matters? The last configuration where six machines have the same hostname in the same
Since I first came upon /etc/hosts, I was told I was supposed to put the short name as the 1st name of the first IP on my first ethernet port. I.e. The short names in your /etc/hosts really should be first on the line unless you want the resolver to return the long name... I mean, how would it know which was the real name? I don't think what you have in /etc/<filename> makes any difference to what the hostname command returns, but with all the changes, it might contact systemd for proper resolution and all bets are off then. ;-) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 07/19/2014 01:42 PM, Linda Walsh wrote:
I don't think what you have in /etc/<filename> makes any difference to what the hostname command returns,
true, it just invokes the uname(2) syscall. You can see with "strace -v hostname". (Of course this is not true for "hostname -f"). Have a nice day, Berny -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Linda Walsh wrote:
Patrick Shanahan wrote:
* David C. Rankin <drankinatty@suddenlinkmail.com> [07-18-14 18:22]:
Are any of you working on networks where this matters? The last configuration where six machines have the same hostname in the same
Since I first came upon /etc/hosts, I was told I was supposed to put the short name as the 1st name of the first IP on my first ethernet port.
I.e. The short names in your /etc/hosts really should be first on the line unless you want the resolver to return the long name...
I mean, how would it know which was the real name?
I don't think what you have in /etc/<filename>
oops ^^^^ /etc/{hostname,HOSTNAME}
makes any difference to what the hostname command returns, but with all the changes, it might contact systemd for proper resolution and all bets are off then. ;-)
I haven't seen HOSTNAME anywhere except SuSE. As for the flags to hostname, don't remember that it had such flags when I first encountered hostname (~1989@sun)
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (9)
-
apc＠abcj.demon.co.uk -
Bernhard Voelker -
David C. Rankin -
Felix Miata -
grantksupport＠operamail.com -
Ken Schneider - openSUSE -
Linda Walsh -
lynn -
Patrick Shanahan