Quack,
On 2019-11-01 19:32, Christoph Biedl wrote:
Let me rephrase: If inspircd is configured to bind to specific
addresses, this binding does not happen if the configuration hasn't
happened (yet). This can be healed by re-ordering the execution order.
Yes, but I expect network availability to be a common requirements for
all configs, thus the binding should not count as requirements.
Can you confirm this does not happen in unstable (3.3.0-1)? I failed to
reproduce the issue there, also the service file unterwent some
changes,
it's now taken from upstream.
Not yet, as I'm traveling.
I can rebuild it for stable and test it in a week or two though.
Nevertheless depending on the following reply that might not be needed.
Please note I've been using both recommended statements using a service
file override and cannot reproduce so far.
Upstream uses "After=network.target" only, basically
https://sources.debian.org/src/inspircd/3.3.0-1/make/template/inspircd.service/
Yes, but as referenced on this other bug systemd upstream recommends
both statements. I see no downside in doing so, so why not go for it?
Regards.
\_o<
--
Marc Dequènes
