bug#66306: Too many services depend on ‘networking’

bug#66306: Too many services depend on ‘networking’

[Ludovic Courtès]

I believe too many services depend on ‘networking’ for no good reason.
There’s a good discussion of the problem at:

  https://systemd.io/NETWORK_ONLINE/

For example, bitlbee, ntpd, hurd-vm, and avahi-daemon all depend on
‘networking’.

Is it always justified?  For example, avahi-daemon unconditionally
listens on 0.0.0.0 and [::], so there’s no need to depend on
‘networking’.

--8<---------------cut here---------------start------------->8---
$ sudo netstat -tupla |grep avahi
udp        0      0 0.0.0.0:mdns            0.0.0.0:*                           650/avahi-daemon: r 
udp6       0      0 [::]:mdns               [::]:*                              650/avahi-daemon: r 
--8<---------------cut here---------------end--------------->8---

In other cases, such as bitlbee, it’s not as obvious because users can
specify different addresses to listen to, and those might depend on
‘networking’ to set up the corresponding interfaces.

Thoughts?  Should we do an audit of these?

Ludo’.

bug#66306: Too many services depend on ‘networking’

[Efraim Flashner]

[-- Attachment #1: Type: text/plain, Size: 1835 bytes --]

On Mon, Oct 02, 2023 at 02:24:49PM +0200, Ludovic Courtès wrote:
> I believe too many services depend on ‘networking’ for no good reason.
> There’s a good discussion of the problem at:
> 
>   https://systemd.io/NETWORK_ONLINE/

This exactly! How much 'network' counts as 'good enough' to start the
next services?

> For example, bitlbee, ntpd, hurd-vm, and avahi-daemon all depend on
> ‘networking’.
> 
> Is it always justified?  For example, avahi-daemon unconditionally
> listens on 0.0.0.0 and [::], so there’s no need to depend on
> ‘networking’.
> 
> --8<---------------cut here---------------start------------->8---
> $ sudo netstat -tupla |grep avahi
> udp        0      0 0.0.0.0:mdns            0.0.0.0:*                           650/avahi-daemon: r 
> udp6       0      0 [::]:mdns               [::]:*                              650/avahi-daemon: r 
> --8<---------------cut here---------------end--------------->8---
> 
> In other cases, such as bitlbee, it’s not as obvious because users can
> specify different addresses to listen to, and those might depend on
> ‘networking’ to set up the corresponding interfaces.
> 
> Thoughts?  Should we do an audit of these?

Probably should do an audit. For bitlbee, I guess the question is how
does it respond to changes in networking? If it comes up when only
loopback is up will it need to be restarted once an actual network shows
up?

For ntpd, I've had trouble with openntpd coming up while only loopback
was active and then I'd have to restart it for it to get the initial big
jump when starting.


-- 
Efraim Flashner   <efraim@flashner.co.il>   רנשלפ םירפא
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]