[systemd-devel] Transient hostname default behaviour

[Zbigniew Jędrzejewski-Szmek]

On Mon, Oct 29, 2012 at 01:38:55PM -0600, Daniel Drake wrote:
> On Mon, Oct 29, 2012 at 1:33 PM, Daniel Drake <dsd at laptop.org> wrote:
> > I'm working on updating OLPC configuration for systemd-195 based on this info:
> > http://lists.fedoraproject.org/pipermail/test/2012-October/111230.html
> >
> > I can't quite figure out the hostname thing.
> 
> One more thing to add:
> 
> It looks like /etc/sysconfig/network is still being parsed even though
> the above link suggests otherwise. Putting HOSTNAME=myhostname in
> /etc/sysconfig/network sets the default transient hostname. Hmm.
Hi,

I am seeing similar behaviour, avahi registers on linux.local.

In the journal, messages are labelled with the hostname... This makes
is fairly easy to spot when the name changes:

Oct 28 13:13:34 localhost avahi-daemon[483]: Server startup complete. Host name is linux.local. Local service cookie is 781387960.
Oct 28 13:13:36 localhost avahi-daemon[483]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.122.254.
Oct 28 13:13:36 localhost avahi-daemon[483]: New relevant interface eth0.IPv4 for mDNS.
Oct 28 13:13:36 localhost avahi-daemon[483]: Registering new address record for 192.168.122.254 on eth0.IPv4.
Oct 28 13:13:36 localhost NET[700]: /usr/sbin/dhclient-script : updated /etc/resolv.conf
Oct 28 13:13:36 fedora-15 network[522]: Determining IP information for eth0...Failed to issue method call: Unit chronyd.service is not loaded.
Oct 28 13:13:36 fedora-15 dhclient[638]: bound to 192.168.122.254 -- renewal in 1611 seconds.

So it seems that here the hostname is set by the network configuration
script.

It _was_ working until a few days ago.

Zbyszek