On Wed, May 05, 2021 at 12:28:56PM +0100, Richard W.M. Jones wrote:
> On Wed, May 05, 2021 at 09:16:38AM +, Zbigniew Jędrzejewski-Szmek wrote:
> > I assume you had 'localhost.localdomain' in /etc/hostname, and now
> > you have 'pick.home.annexia.org' after the call to 'hostnamectl
> > set-hostn
On Wed, May 05, 2021 at 09:16:38AM +, Zbigniew Jędrzejewski-Szmek wrote:
> I assume you had 'localhost.localdomain' in /etc/hostname, and now
> you have 'pick.home.annexia.org' after the call to 'hostnamectl
> set-hostname'. This sounds like a bug in NM then, because the static
> configuration
On Wed, May 05, 2021 at 10:03:29AM +0100, Richard W.M. Jones wrote:
> On Wed, May 05, 2021 at 09:41:48AM +0100, Richard W.M. Jones wrote:
> >
> > No idea what particular component / update caused that though,
> > or even how to find out.
>
> So it started with:
>
> localhost.localdomain systemd-
On Wed, May 05, 2021 at 09:41:48AM +0100, Richard W.M. Jones wrote:
>
> No idea what particular component / update caused that though,
> or even how to find out.
So it started with:
localhost.localdomain systemd-hostnamed[1796302]: Hostname set to
(static)
but this seems uncorrelated with any
No idea what particular component / update caused that though,
or even how to find out.
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-top is 'top' for virtual machines. Tiny pro
