> > The dhclient exit hook script 'hostname' fails to be executed in some
> > cases due to the hardcoded (wrong) path to arping in package
> > network-manager.
> >
> > network-manager-0.9.10.0/src/devices/nm-device.c:
> >
> > const char *argv[] = { "/sbin/arping", mode_arg, "-q", "-I",
> > nm_device_get_ip_iface (self), "-c", "1", NULL, NULL };
>
> jessie currently has:
>
> $ apt-file search bin/arping
> arping: /usr/sbin/arping
> iputils-arping: /usr/bin/arpingDebian Edu uses the second by default. > You said it "sometimes fails to be executed" - and I wonder which are the > circumstances when it succeeds? Should have been correctly: 'fails to set the hostname using the network interface IP address.' Not quite sure, but I guess this will always be the case. As far as I understand the involved steps, the hook script doesn't get the IP. The IP should be passed over to the script by Network-Manager using /etc/NetworkManager/dispatcher.d/02debian-edu-config which fails, most probably due to the wrong arping path in the network-manager code. I noticed the error after executing: 'systemctl status NetworkManager.service -l' > Also, what is the effect on Debian Edu? I wonder whether the severity of > #755997 should be upgraded... If a hostname is set via GOsa² for a new system (as replacement for the automac-XXX hostname) the new hostname should be set after rebooting the new machine. This fails and will confuse the local admin(s). Wolfgang
signature.asc
Description: Digital signature
