[Pkg-systemd-maintainers] Systemd & DNS resolution
Michael Stapelberg
stapelberg at debian.org
Wed Feb 26 07:41:43 GMT 2014
Hi Tomasz,
Tomasz Buchert <tomasz.buchert at inria.fr> writes:
> I have this bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739363
>
> There are two issues:
>
> 1) how can I wait for DNS resolution to be available before
> running my service? (this causes the bug above)
You shouldn’t, ideally. Services should be able to deal with changes in
network configuration, such as ethernet interfaces
appearing/disappearing and global connectivity showing up/getting lost
at any point in time. I realize that it’s not always easy to fix
services in that regard, but it’s a good idea to do it.
That said, you could use After=NetworkManager-wait-online.service with
the caveat that it only works for NetworkManager users.
I am not aware of any other way.
> 2) it seems that "systemctl status" does not capture
> all output (stderr in that case) from ExecStartPre=
> command (it can be seen in journalctl, though); are
> you aware of this ... bug?
I’m not sure why this is, but then, in #739363, much information is
missing to make even an educated guess about it (e.g. the output of
systemctl dump, the systemd/journald version, …). If you care (and can
reproduce it), feel free to file a separate ticket about it.
--
Best regards,
Michael
More information about the Pkg-systemd-maintainers
mailing list