On Sun, Dec 8, 2024 at 8:00 AM Adam Nielsen wrote:
>
> Hi all,
>
> Is there a way to tell the systemd-networkd-wait-online service to wait
> until DNS is working before continuing?
>
I have a PR open for this, which should hopefully be in v258.
https://github.com/systemd/systemd/pull/34640
-NR
> > Is there a way to tell the systemd-networkd-wait-online service to wait
> > until DNS is working before continuing?
>
> There is not, so I built a small tool for this:
> https://forge.km6g.us/km6g/wait-for-dns
>
> It doesn't just wait for a DNS resolver to be configured, it waits for a nam
On Sun, Dec 8, 2024, at 06:47, Adam Nielsen wrote:
> Hi all,
>
> Is there a way to tell the systemd-networkd-wait-online service to wait
> until DNS is working before continuing?
There is not, so I built a small tool for this:
https://forge.km6g.us/km6g/wait-for-dns
It doesn't just wait for a DN
Hi all,
Is there a way to tell the systemd-networkd-wait-online service to wait
until DNS is working before continuing?
I have an issue where I need an NFS share mounted during boot, but the
automount process is failing because the "mount" command can't resolve
the hostname of the server during b
On 27 March 2018 at 10:22, Colin Guthrie wrote:
> Dimitri John Ledkov wrote on 26/03/18 11:34:
>> Hello,
>>
>> When systemd-networkd-wait-online was originally introduced, it was
>> the only tool that correctly waited and blocked the boot, until after
>> networking is configured.
>>
>> These days,
Dimitri John Ledkov wrote on 26/03/18 11:34:
> Hello,
>
> When systemd-networkd-wait-online was originally introduced, it was
> the only tool that correctly waited and blocked the boot, until after
> networking is configured.
>
> These days, however, all/most network configurations tools ship
> a
Hello,
When systemd-networkd-wait-online was originally introduced, it was
the only tool that correctly waited and blocked the boot, until after
networking is configured.
These days, however, all/most network configurations tools ship
appropriate wait-online integration. E.g. there is network-man
On Fr, 08.12.17 20:54, Johannes Ernst ([email protected]) wrote:
> Thanks. I’m not surprised that work remains ...
>
> Related question: systemd-networkd-wait-online.target seems to
> assume that once the network is online, it stays that way. I’d like
> to also take action when it goes dow
Thanks. I’m not surprised that work remains ...
Related question: systemd-networkd-wait-online.target seems to assume that once
the network is online, it stays that way. I’d like to also take action when it
goes down, and again when it comes back up. Any pointers how to best go about
this? Is t
On Di, 05.12.17 12:21, Johannes Ernst ([email protected]) wrote:
See the discussion on
https://github.com/systemd/systemd/issues/7478#issuecomment-348508263
regarding this kind of hardware.
Lennart
--
Lennart Poettering, Red Hat
___
systemd-dev
I’m running systemd 235.38 on an ARM64 device called the EspressoBin [1]. The
EspressoBin board has an on-board Ethernet switch, which I configure with
systemd-networkd (configuration is below). The device is intended as a home
router that runs IPv4 masquerading, local DNS server etc.
I’m attem
goes back to 'can we have a configurable script to run when DHCP assigns
the address?'
Surely it can't be that hard to read a config line, save it, and later
execute a script
On Tue, Sep 6, 2016 at 1:54 PM, Ernst Bammer wrote:
> Hi,
> sorry to bring this up again, but maybe somebody is back fro
Hi,
sorry to bring this up again, but maybe somebody is back from vacation
who can answer this? ;-)
Best regards, Ernst
On Sun, Jul 24, 2016 at 12:31 PM, Ernst Bammer wrote:
> Hi,
>
> I have a service that depends on a non-loopback IPv4 address to be
> available at start-up. My network configurat
Hi,
I have a service that depends on a non-loopback IPv4 address to be
available at start-up. My network configuration is done with networkd,
it's very simple and basically just:
[Match]
Name=eth*
[Network]
DHCP=v4
I've added the following to my service:
[Unit]
Requires=network-online.target
Af
2014-06-25 14:12 GMT+04:00 Michael Olbrich :
> Hi,
>
> Commit 58e027023b47b32e42cf93dd4a629b869ee1ef25 'units: order
> network-online.target after network.target' added "Before=network.target"
> dependency to systemd-networkd-wait-online.service. Is that correct? If I
> understand the documentation
On Mon, Jun 30, 2014 at 1:04 PM, Lennart Poettering
wrote:
> On Sun, 29.06.14 23:58, Tom Gundersen ([email protected]) wrote:
>
>>
>> On Wed, Jun 25, 2014 at 12:12 PM, Michael Olbrich
>> wrote:
>> > Commit 58e027023b47b32e42cf93dd4a629b869ee1ef25 'units: order
>> > network-online.target after network.
On Sun, 29.06.14 23:58, Tom Gundersen ([email protected]) wrote:
>
> On Wed, Jun 25, 2014 at 12:12 PM, Michael Olbrich
> wrote:
> > Commit 58e027023b47b32e42cf93dd4a629b869ee1ef25 'units: order
> > network-online.target after network.target' added "Before=network.target"
> > dependency to systemd-net
On Wed, Jun 25, 2014 at 12:12 PM, Michael Olbrich
wrote:
> Commit 58e027023b47b32e42cf93dd4a629b869ee1ef25 'units: order
> network-online.target after network.target' added "Before=network.target"
> dependency to systemd-networkd-wait-online.service. Is that correct? If I
> understand the document
Hi,
Commit 58e027023b47b32e42cf93dd4a629b869ee1ef25 'units: order
network-online.target after network.target' added "Before=network.target"
dependency to systemd-networkd-wait-online.service. Is that correct? If I
understand the documentation correctly, then network.target should not be
delayed. M
19 matches
Mail list logo
