Hi Thomas,
> > But what should it do if it can't?
>
> IMO, it should bind on everything configured if it's there. If not, then
> the daemon should still start, and continue to attempt binding until the
> configured IP is available.
That makes me a little uncomfortable as it therefore definitely
requires a port-supporting monitoring system to test whether it is
really available to serve clients, rather than simply being able to
rely on whether the process is up and running.
Putting it crudely, systemd would say "Running" when it wasn't really
"running" in any meaningful sense of the word.
(Sure, you might have such a monitoring system in any Real World
scenario, but still...)
> What if for some reason a configured IP isn't available yet at the time
> of server boot? This happens often with some nasty switched like Cisco
> Catalyst if configured without port-fast.
(Isn't there some kind of network-online.target specifically for this?)
> the default should be 127.0.0.0 without ::1 if that can't always work.
^
Could you elaborate?
Ah, one thing that might not be clear is that the addition of ::1 to
the config file is a Debian-specific change introduced via #891432.
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
