On Wed, 2013-09-25 at 10:26 -0600, Chris Murphy wrote: > On Sep 25, 2013, at 2:41 AM, Adam Williamson <awill...@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. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
