Hi Ian, On Jul 17 19:23, Ian Chapman wrote: > On 17/07/14 18:45, Corinna Vinschen wrote: > >On Jul 17 18:32, Ian Chapman wrote: > >>Hi, > >> > >>Dhcpd on my server has suddenly started taking to start before the IP > >>address (statically assigned) has been configured on the network interface > >>and consequently bombs out. The systemd service for dhcpd has > >> > >>After=network.target > >> > >> > >>should this be network-online.target? > > > >Probably, or dhcpd needs to set the IP_FREEBIND socket option. > > The important > >thing here is that you fill in the "Blocks" field with the number of the > >tracker bug 1119787, so this can be followed through. > > Changing from After=network.target to After=network-online.target seems to > work around the problem. I've filed a bug against dhcpd as you suggested. > Unfortunately it looks like Bind might be affected too, whilst it starts on > boot, it doesn't respond to clients resolution requests until I manually > restart the service after boot. I'll look a bit deeper into that one too and > consider a bug report. I already reported the bind problem yesterday: https://bugzilla.redhat.com/show_bug.cgi?id=1119815 Have a look at the tracker bug https://bugzilla.redhat.com/show_bug.cgi?id=1119787 It contains a list of dependent bug reports. The current list contains bug reports against bind, dovecot, ejabberd, openssh, postfix, radicale, and even an old bug report of mine against the initscripts network service. Corinna -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
