Le 13/10/2023 à 16:01, tito via Dng a écrit :
> # TEST NETWORK
> NETWORK=$(printf "GET /nm HTTP/1.1\\r\\nHost: network-test.debian.org\\r\\n\\r\\n" | nc -w1 network-test.debian.org 80 | grep -c "NetworkManager is online")
> if test "$NETWORK" -ne 1 ; then
> NETWORK=$(printf "GET /ncsi.txt HTTP/1.1\\r\\nHost:www.msftncsi.com\\r\\n\\r\\n" | nc -w1www.msftncsi.com 80 | grep -c "Microsoft NCSI")
> if test "$NETWORK" -ne 1 ; then
> echo "Your network seems to be down. "
> echo "Cannot connect to the Internet. Exiting..."
> exit 1
> fi
> else
> echo "Network Connectivity Status: OK"
> fi
>
> OTOH maybe network is to be intended as device lo
> so that just 127.0.0.1 is up as you cannot have
> a guarantee that the box is even connected to the
> network
>
> or it is to be intended as bring up all interfaces
> in /etc/network/interfaces?
I think services such as ssh, http, dns, avahi or cups servers can
survive deconfiguration/reconfiguration of interfaces; in addition, they
might be used only in a LAN. I guess they can be started anytime, not
needing at all to wait for network configuration. It seems to me that
this hair of dependencies is a little bit of an exageration. With s6,
AFAIU, there needs not even be a dependency on syslog since I've read
that the concept is to pipe the logs back to s6.
-- Didier
::
Re: [DNG] powerdns upstream has dro…
