[systemd-devel] systemd and hostname supplied by DHCP

[Tomasz Torcz]

On Fri, Oct 02, 2015 at 02:00:21PM +0200, Alessio Igor Bogani wrote:
> Hi,
> 
> On 29 September 2015 at 13:53, Alessio Igor Bogani
> <alessioigorbogani at gmail.com> wrote:
> > Hi David,
> >
> > On 28 September 2015 at 16:05, David Timothy Strauss
> > <david at davidstrauss.net> wrote:
> >> On Mon, Sep 28, 2015 at 1:19 AM Alessio Igor Bogani
> >> <alessioigorbogani at gmail.com> wrote:
> > [...]
> >>> The systemd 219 brought with Yocto "Fido" can't set hostname supplied
> >>> by DHCP on my Beaglebone:
> > [...]
> >> "Could not set hostname: No route to host" sounds like systemd is trying to
> >> resolve and ping the provided hostname. But, it's failing, and so systemd is
> >> deciding that it's not a usable hostname. Doesn't seem related to the DHCP
> >> protocol implementation at all.
> 
> If I enable debug:
> Oct 02 08:10:43 localhost systemd-networkd[277]: Got message
> type=error sender=:1.4 destination=:1.2 object=n/a interface=n/a
> member=n/a cookie=5 reply_cookie=12 error=The name
> org.freedesktop.PolicyKit1 was not provided by any .service files
> Oct 02 08:10:43 localhost systemd-networkd[277]: eth0: Could not set
> hostname: No route to host

  My guess: do you have hostnamed installed?

-- 
Tomasz Torcz       ,,(...) today's high-end is tomorrow's embedded processor.''
xmpp: zdzichubg at chrome.pl                      -- Mitchell Blank on LKML