Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #206286
| From | Markus Schönhaber <debian-user@list-post.mks-mail.de> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: systemd: how to start a service (kea DHCP4) after all network interfaces are up? |
| Date | 2019-03-17 17:20 +0100 |
| Message-ID | <xCGFX-6aM-3@gated-at.bofh.it> (permalink) |
| References | <xCfZ7-3w0-3@gated-at.bofh.it> <xChHz-4DC-1@gated-at.bofh.it> <xCmnU-7CO-7@gated-at.bofh.it> <xCo6l-k0-3@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Sven Joachim, 16.3.2019 21:11 +0100: > On 2019-03-16 19:20 +0100, Markus Schönhaber wrote: > >> John Doe, 16.3.2019 14:18 +0100: >> >>> If your interface is configured by 'systemd', you could try: >>> >>> $ systemctl enable systemd-networkd-wait-online >> >> Thanks, but no, my network configuration is done through >> /etc/network/interfaces. Therefore this won't help. > > Try "systemctl enable ifupdown-wait-online.service" then. > See bug #912112[1]. Thanks for the info! But alas, since I'm on stretch, it isn't that easy, since the ifupdown package there provides neither the ifupdown-wait-online.service file nor the wait-online.sh script. I've downloaded the .deb for buster and tried to extract the relevant files from there and install them on my system, but I didn't manage to get that working in a way that the DHCP server was kept from starting too early. Due to the lack of time I'll refrain from trying to find out what I may have done wrong. And since there seems to be no out-of-the-box solution for this problem on stretch anyway, I'll stick to my ugly workaround for now and hope this will be sorted out in buster. That said, thanks again for pointing me in the right direction! -- Regards mks
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
systemd: how to start a service (kea DHCP4) after all network interfaces are up? Markus Schönhaber <debian-user@list-post.mks-mail.de> - 2019-03-16 12:50 +0100
Re: systemd: how to start a service (kea DHCP4) after all network interfaces are up? john doe <johndoe65534@mail.com> - 2019-03-16 14:40 +0100
Re: systemd: how to start a service (kea DHCP4) after all network interfaces are up? Markus Schönhaber <debian-user@list-post.mks-mail.de> - 2019-03-16 19:40 +0100
Re: systemd: how to start a service (kea DHCP4) after all network interfaces are up? Sven Joachim <svenjoac@gmx.de> - 2019-03-16 21:30 +0100
Re: systemd: how to start a service (kea DHCP4) after all network interfaces are up? Markus Schönhaber <debian-user@list-post.mks-mail.de> - 2019-03-17 17:20 +0100
Re: systemd: how to start a service (kea DHCP4) after all network interfaces are up? Greg Wooledge <wooledg@eeg.ccf.org> - 2019-03-18 13:50 +0100
Re: systemd: how to start a service (kea DHCP4) after all network interfaces are up? Markus Schönhaber <debian-user@list-post.mks-mail.de> - 2019-03-18 14:30 +0100
Re: systemd: how to start a service (kea DHCP4) after all network interfaces are up? Curt <curty@free.fr> - 2019-03-18 18:50 +0100
Re: systemd: how to start a service (kea DHCP4) after all network interfaces are up? Henning Follmann <hfollmann@itcfollmann.com> - 2019-03-18 20:30 +0100
Re: systemd: how to start a service (kea DHCP4) after all network interfaces are up? Markus Schönhaber <debian-user@list-post.mks-mail.de> - 2019-03-18 21:00 +0100
csiph-web