https://dl.dropboxusercontent.com/u/3253801/IMG_20130924_185026.jpg
Settings>System: Details
a. Device name is showing hostnamectl transient name, not static name. I just tried this in F19 and it shows the static name. So this seems backwards now with Gnome 3.9.
b. Disk value is 1.4TB. This computer has a 500GB drive in it and that's it. No LVM thinp is being used either.
Both seem like cosmetic bugs, yes? File in bugzilla or upstream with gnome?
Chris Murphy
On Tue, 2013-09-24 at 23:11 -0600, Chris Murphy wrote:
https://dl.dropboxusercontent.com/u/3253801/IMG_20130924_185026.jpg
Settings>System: Details
a. Device name is showing hostnamectl transient name, not static name. I just tried this in F19 and it shows the static name. So this seems backwards now with Gnome 3.9.
How to reproduce ?
b. Disk value is 1.4TB. This computer has a 500GB drive in it and that's it. No LVM thinp is being used either.
Weird..
Both seem like cosmetic bugs, yes? File in bugzilla or upstream with gnome?
Fill to BGO (bugzilla.gnome.org) please.
Chris Murphy
On Sep 25, 2013, at 12:00 AM, Igor Gnatenko i.gnatenko.brain@gmail.com wrote:
On Tue, 2013-09-24 at 23:11 -0600, Chris Murphy wrote:
https://dl.dropboxusercontent.com/u/3253801/IMG_20130924_185026.jpg
Settings>System: Details
a. Device name is showing hostnamectl transient name, not static name. I just tried this in F19 and it shows the static name. So this seems backwards now with Gnome 3.9.
How to reproduce ?
Baremetal: hostnamectl set-hostname f20s.localdomain --static hostnamectl set-hostname oldmac.localdomain --transient
On every boot, Gnome says the Device name is oldmac.localdomain. On a VM of F19, Gnome uses f19s.localdomain rather than vbox.localdomain.
Actually I probably ought to ask which of these even ought to be set. I find the idea of static, pretty and transient hostnames thoroughly confusing. I'm not setting a pretty hostname, btw.
Chris Murphy
On 09/25/2013 09:11 AM, Chris Murphy issued this missive:
On Sep 25, 2013, at 12:00 AM, Igor Gnatenko i.gnatenko.brain@gmail.com wrote:
On Tue, 2013-09-24 at 23:11 -0600, Chris Murphy wrote:
https://dl.dropboxusercontent.com/u/3253801/IMG_20130924_185026.jpg
Settings>System: Details
a. Device name is showing hostnamectl transient name, not static name. I just tried this in F19 and it shows the static name. So this seems backwards now with Gnome 3.9.
How to reproduce ?
Baremetal: hostnamectl set-hostname f20s.localdomain --static hostnamectl set-hostname oldmac.localdomain --transient
On every boot, Gnome says the Device name is oldmac.localdomain. On a VM of F19, Gnome uses f19s.localdomain rather than vbox.localdomain.
Actually I probably ought to ask which of these even ought to be set. I find the idea of static, pretty and transient hostnames thoroughly confusing. I'm not setting a pretty hostname, btw.
The commands should be:
hostnamectl --static set-hostname f20s.localdomain hostnamectl --transient set-hostname oldmac.localdomain
Not sure what happens if you place the options after the commands. The default is to set ALL hostnames to that specified so if the command is ignoring the option (because it's at the end), the last "hostnamectl" command you specified (in this case, oldmac.localdomain) becomes the pretty, transient AND static name. More or less what you're seeing.
You should also check /etc/hosts to see if there's an entry in there for 127.0.0.1 referring to oldmac.localdomain. Also keep in mind that a number of the utilities do reverse DNS lookups instead of using the hostname bits so you may be seeing a DNS artifact here. ---------------------------------------------------------------------- - Rick Stevens, Systems Engineer, AllDigital ricks@alldigital.com - - AIM/Skype: therps2 ICQ: 22643734 Yahoo: origrps2 - - - - "Do you suffer from long-term memory loss?" "I don't remember" - - -- Chumbawumba, "Amnesia" (TubThumping) - ----------------------------------------------------------------------
On Sep 25, 2013, at 10:48 AM, Rick Stevens ricks@alldigital.com wrote:
The commands should be:
hostnamectl --static set-hostname f20s.localdomain hostnamectl --transient set-hostname oldmac.localdomain
Not sure what happens if you place the options after the commands.
Yes I see in the man page that I have this reversed, but if it's a problem with superfluous or misunderstood information and it doesn't give me an error, that's a bug. So far I'm not seeing any difference in behavior with the order of the commands.
The default is to set ALL hostnames to that specified so if the command is ignoring the option (because it's at the end), the last "hostnamectl" command you specified (in this case, oldmac.localdomain) becomes the pretty, transient AND static name. More or less what you're seeing.
No, the most recent command set transient to oldmac.localdomain which is then not used for ssh, and not listed with a subsequent hostnamectl, and is only used by Gnome. Everything else shows the static hostname set with the first command.
You should also check /etc/hosts to see if there's an entry in there for 127.0.0.1 referring to oldmac.localdomain.
[root@f20s ~]# cat /etc/hostname f20s.localdomain
Also keep in mind that a number of the utilities do reverse DNS lookups instead of using the hostname bits so you may be seeing a DNS artifact here.
Router running Tomato firmware lists the NIC MAC and IP with Name = f20s so at this point only Gnome is referencing this oldmac.localdomain thing. I might try changing it and see what gets changed elsewhere.
Chris Murphy
On Sep 25, 2013, at 10:48 AM, Rick Stevens ricks@alldigital.com wrote:
hostnamectl --static set-hostname f20s.localdomain hostnamectl --transient set-hostname oldmac.localdomain
OK so just did that and now I'm getting different behavior.
1. man hostnamectl says "The static hostname is stored in /etc/hostname, see hostname(5) for more information." And yet
[root@f20s ~]# hostname oldmac.localdomain [root@f20s ~]# hostname -f hostname: Name or service not known [root@f20s ~]# cat /etc/hostname f20s.localdomain
2. If I ssh to oldmac.local I get a "could not resolve hostname" message, if I ssh to f20s.local it works, yet I now get an oldmac prompt after logging out and back in:
[root@oldmac ~]#
3. If I restart Avahi, now I have to ssh to oldmac.local instead of f20s.local. I cannot ssh to either oldmac.localdomain or f20s.localdomain, I get a "could not resolve hostname" message.
4. Gnome is still set to oldmac.localdomain.
Psychopathically complicated. Thanks Adam.
Chris Murphy
On Sep 25, 2013, at 11:23 AM, Chris Murphy lists@colorremedies.com wrote:
On Sep 25, 2013, at 10:48 AM, Rick Stevens ricks@alldigital.com wrote:
hostnamectl --static set-hostname f20s.localdomain hostnamectl --transient set-hostname oldmac.localdomain
OK so just did that and now I'm getting different behavior.
- man hostnamectl says "The static hostname is stored in /etc/hostname, see hostname(5) for more information." And yet
[root@f20s ~]# hostname oldmac.localdomain [root@f20s ~]# hostname -f hostname: Name or service not known [root@f20s ~]# cat /etc/hostname f20s.localdomain
- If I ssh to oldmac.local I get a "could not resolve hostname" message, if I ssh to f20s.local it works, yet I now get an oldmac prompt after logging out and back in:
[root@oldmac ~]#
If I restart Avahi, now I have to ssh to oldmac.local instead of f20s.local. I cannot ssh to either oldmac.localdomain or f20s.localdomain, I get a "could not resolve hostname" message.
Gnome is still set to oldmac.localdomain.
**snicker**
I rebooted, changing nothing else. Now I can't ssh in as oldmac.local, I have to use f20s.local. And now transient doesn't show up. So if I change things, I get some changes in behavior. If I restart processes, I get more changes in behavior. If I reboot, I get a complete reversal of behavior back to the way things were before any of the changes I made. This is a mess, honestly. I think the thing to do is set --static and leave everything else alone.
[root@f20s ~]# hostnamectl Static hostname: f20s.localdomain Icon name: computer-laptop Chassis: laptop Machine ID: 8e4cbfea404512ae70096c6202c9a3bf Boot ID: 23cbdff8e1bf4ce9ac26ecc897b8447c Operating System: Fedora 20 (Heisenbug) CPE OS Name: cpe:/o:fedoraproject:fedora:20 Kernel: Linux 3.12.0-0.rc2.git0.1.fc21.x86_64 Architecture: x86_64
[root@f20s ~]# hostname f20s.localdomain
[root@f20s ~]# hostname -f hostname: Name or service not known
[root@f20s ~]# cat /etc/hostname f20s.localdomain
Chris Murphy
On Wed, 2013-09-25 at 14:37 -0600, Chris Murphy wrote:
I rebooted, changing nothing else. Now I can't ssh in as oldmac.local, I have to use f20s.local. And now transient doesn't show up. So if I change things, I get some changes in behavior. If I restart processes, I get more changes in behavior. If I reboot, I get a complete reversal of behavior back to the way things were before any of the changes I made. This is a mess, honestly. I think the thing to do is set --static and leave everything else alone.
I think that is usually a valid approach, as I understand it at present, yeah. The only thing likely to set the transient hostname is DHCP, and if you explicitly specify a static hostname, DHCP will not override it; AIUI, all the Fedora networking bits are configured to only set the hostname from DHCP if there is no explicitly user-configured hostname.
Note, one thing I found screwing with hostnamectl's story of how hostname setting works is dracut: if you set /etc/hostname once and then wiped it you might think you've un-set the static hostname, but your initramfs likely contains a copy, and it looks like dracut sets the hostname specified in its copy of /etc/hostname during early boot.
(I was trying to get my systems' hostnames set via dhcp in a reliable way; this seems to be extremely difficult, and for now I've given up and am just brute forcing the 'correct' values. The closest I got was that each system would boot with 'hostname' returning 'machine' and 'hostname -f' returning 'hostname.happyassassin.net', but this apparently isn't enough for freeipa, which expects 'hostname' to return 'hostname.happyassassin.net' . This hostname stuff is so complicated I don't even know whether I should claim that's a bug on freeipa's part - that anything which requires an FQDN should do the syscall equivalent of 'hostname -f' - or not.)
On 09/25/13 13:11, Chris Murphy wrote:
https://dl.dropboxusercontent.com/u/3253801/IMG_20130924_185026.jpg
Settings>System: Details
a. Device name is showing hostnamectl transient name, not static name. I just tried this in F19 and it shows the static name. So this seems backwards now with Gnome 3.9.
Just installed the Alpha. Gnome Version shows as 3.9.92 and I get the "correct" hostname.domain.com which I set using hostnamectl.
b. Disk value is 1.4TB. This computer has a 500GB drive in it and that's it. No LVM thinp is being used either.
Using a VM and the disk size appears correct.
On Tue, 2013-09-24 at 23:11 -0600, Chris Murphy wrote:
https://dl.dropboxusercontent.com/u/3253801/IMG_20130924_185026.jpg
Settings>System: Details
a. Device name is showing hostnamectl transient name, not static name. I just tried this in F19 and it shows the static name. So this seems backwards now with Gnome 3.9.
By my understanding, if there's a 'transient' hostname then it is likely to be the currently "active" hostname, not the 'static' one. The 'static' one is kind of a permanent fallback value which can possibly get overwritten by a 'transient' one on network init, but the 'static' one is tracked because that's what the hostname will fall back to if the 'transient' one goes away for some reason.
(At least, that's my best understanding ATM. I've been poking this stuff lately in the context of getting IPA set up, and I suspect hostname is a bit like xkb - seems simple on the surface, turns out to be pyschopathically complicated when you get into the details. There seem to be three different kernel syscalls for 'querying the hostname', which can all return different results in different circumstances. Try 'hostname' and 'hostname -f'...)
On Sep 25, 2013, at 2:41 AM, Adam Williamson awilliam@redhat.com wrote:
By my understanding, if there's a 'transient' hostname then it is likely to be the currently "active" hostname, not the 'static' one.
Well that's a problem. Linguistically transient means impermanent, so it should be the least likely hostname compared to static.
Also, on this same machine that Gnome uses the transient name for, I must use the static name when ssh'ing into it. So apparently Avahi is using the static hostname, which is what I'm expecting. But Gnome isn't. For me. Because Ed is saying it's using static for him, not transient.
The 'static' one is kind of a permanent fallback value which can possibly get overwritten by a 'transient' one on network init, but the 'static' one is tracked because that's what the hostname will fall back to if the 'transient' one goes away for some reason.
Oh dear sweet mother of leaping lizards all choking on a stick.
Now, after having set separate --static and --transient hostnames with hostnamectl, on reboots it never appears in hostnamectl. It was only there briefly after having set it, and then polling it right after.
Maybe I shouldn't be setting one of these. Doesn't anaconda only set static?
(At least, that's my best understanding ATM. I've been poking this stuff lately in the context of getting IPA set up, and I suspect hostname is a bit like xkb - seems simple on the surface, turns out to be pyschopathically complicated when you get into the details.
I'm thinking networking in general is psychopathically complicated, which is why there are an increasing number of people getting PhDs in this field. Or maybe that's what's causing it to become psychopathically complicated.
I'm thinking the local router, whether it has local DNS on or not, dnsmasq on or not, etc. etc. is a factor also. I once had some version of dd-wrt that would cause a LiveCD booted F17 or F18 to name itself the hostname for that same machine when it was booted in OSX. So OS X told the router something about its hostname, and then some conversation between the router and Fedora XX occurred even when booting off Live media to set the hostname of the live session.
There seem to be three different kernel syscalls for 'querying the hostname', which can all return different results in different circumstances. Try 'hostname' and 'hostname -f'…)
[root@f20s ~]# hostname f20s.localdomain [root@f20s ~]# hostname -f hostname: Name or service not known [root@f20s ~]# hostnamectl Static hostname: f20s.localdomain Icon name: computer-laptop Chassis: laptop Machine ID: 8e4cbfea404512ae70096c6202c9a3bf Boot ID: 1c344d5b57f24088adf3e29da63ca966 Operating System: Fedora 20 (Heisenbug) CPE OS Name: cpe:/o:fedoraproject:fedora:20 Kernel: Linux 3.12.0-0.rc2.git0.1.fc21.x86_64 Architecture: x86_64
Meanwhile Gnome still says oldmac.localdomain. Cute…
Chris Murphy
On Wed, 2013-09-25 at 10:26 -0600, Chris Murphy wrote:
On Sep 25, 2013, at 2:41 AM, Adam Williamson awilliam@redhat.com wrote:
By my understanding, if there's a 'transient' hostname then it is likely to be the currently "active" hostname, not the 'static' one.
Well that's a problem. Linguistically transient means impermanent, so it should be the least likely hostname compared to static.
Also, on this same machine that Gnome uses the transient name for, I must use the static name when ssh'ing into it. So apparently Avahi is using the static hostname, which is what I'm expecting. But Gnome isn't. For me. Because Ed is saying it's using static for him, not transient.
The 'static' one is kind of a permanent fallback value which can possibly get overwritten by a 'transient' one on network init, but the 'static' one is tracked because that's what the hostname will fall back to if the 'transient' one goes away for some reason.
Oh dear sweet mother of leaping lizards all choking on a stick.
Now, after having set separate --static and --transient hostnames with hostnamectl, on reboots it never appears in hostnamectl. It was only there briefly after having set it, and then polling it right after.
Maybe I shouldn't be setting one of these.
By the description in 'man hostnamectl' that's what it sounds like to me, but then I don't understand why hostnamectl offers you the possibility of setting it in the first place. This does seem like a thoroughly confusing area.
On Tue, 2013-09-24 at 23:11 -0600, Chris Murphy wrote:
https://dl.dropboxusercontent.com/u/3253801/IMG_20130924_185026.jpg
Settings>System: Details
a. Device name is showing hostnamectl transient name, not static name. I just tried this in F19 and it shows the static name. So this seems backwards now with Gnome 3.9.
The code thats showing the hostname is here: https://git.gnome.org/browse/gnome-control-center/tree/shell/cc-hostname-ent... It hasn't changed since it was introduced.
b. Disk value is 1.4TB. This computer has a 500GB drive in it and that's it. No LVM thinp is being used either.
What does gvfs-info -f / report ?
On Sep 25, 2013, at 11:52 AM, Matthias Clasen mclasen@redhat.com wrote:
What does gvfs-info -f / report ?
[root@f20s ~]# gvfs-info -f / attributes: filesystem::size: 464519168000 filesystem::free: 459891695616 filesystem::type: btrfs filesystem::used: 3916201984
Chris Murphy
On Sep 25, 2013, at 11:52 AM, Matthias Clasen mclasen@redhat.com wrote:
On Tue, 2013-09-24 at 23:11 -0600, Chris Murphy wrote:
https://dl.dropboxusercontent.com/u/3253801/IMG_20130924_185026.jpg
Settings>System: Details
a. Device name is showing hostnamectl transient name, not static name. I just tried this in F19 and it shows the static name. So this seems backwards now with Gnome 3.9.
The code thats showing the hostname is here: https://git.gnome.org/browse/gnome-control-center/tree/shell/cc-hostname-ent... It hasn't changed since it was introduced.
Yeah OK, it maybe systemd is now much more transient about the transient hostname. Because on reboot, transient hostname is missing, and Gnome shell doesn't use it anymore, it's using static. So just due to a reboot, Gnome shell Device name is different. It holds onto the transient hostname as long as that session is alive, apparently inheriting the transient name if it was present when gnome-shell launched.
But more hilarity ensues when I use Gnome shell to change Device name. Static hostname is shifted to transient hostname, the entered name becomes the pretty name, and static has a - added to it in a way that makes no sense compared to the former name.
To keep it simple, try this:
1. # hostnamectl set-hostname local.localdomain # reboot
Now I'm in the default state after installing Fedora 20. Gnome shell reports Device name as local.localdomain. And…
[root@local ~]# hostnamectl Static hostname: local.localdomain
2. ssh root@local.local [root@local ~]#
No problems so far.
3. In Gnome shell, change Device name from local.localdomain to gnome.localdomain and all hell breaks loose.
4. hostnamectl reports: [root@local ~]# hostnamectl Static hostname: gnome-localdomain Pretty hostname: gnome.localdomain Transient hostname: local.localdomain
What a mess. And I can't ssh into either local.local or gnome.local. I have to use gnome-localdomain.local, confirmed by the journal:
gnome-localdomain avahi-daemon[345]: Server startup complete. Host name is gnome-localdomain.local. Local service c…09366.
So previously static name is displayed as local.localdomain, but if I change that to gnome.localdomain static becomes gnome-localdomain which then Avahi uses to set its hostname to gnome-localdomain.local. Messy. I think Gnome is either displaying things wrong or setting them wrong or both.
Chris Murphy
On Wed, 2013-09-25 at 15:27 -0600, Chris Murphy wrote:
But more hilarity ensues when I use Gnome shell to change Device name. Static hostname is shifted to transient hostname, the entered name becomes the pretty name, and static has a - added to it in a way that makes no sense compared to the former name.
GNOME Shell has some rather absurd rules about what it considers valid for the 'static' name:
https://bugzilla.gnome.org/show_bug.cgi?id=700846
On Sep 25, 2013, at 11:52 AM, Matthias Clasen mclasen@redhat.com wrote:
b. Disk value is 1.4TB. This computer has a 500GB drive in it and that's it. No LVM thinp is being used either.
What does gvfs-info -f / report ?
Filed as:
https://bugzilla.gnome.org/show_bug.cgi?id=708786
Chris Murphy
-
Adam Williamson -
Chris Murphy -
Ed Greshko -
Igor Gnatenko -
Matthias Clasen -
Rick Stevens