The subservices (bgpd, ripd, ...) are all integrated after zebra in between the same to network-pre/network and bind start/stop to zebra itself
BindsTo=zebra.service
Wants=network.target
After=zebra.service network-pre.target
Before=network.target
That said the issue you mentioned is fixed in newer releases as you assumed.
So let us look at the older releases.
Changing the dependencies of these releases now - as outlined there are cases that can need that - will be too much regression risk.
Suggesting a comment in the config/init is a nice suggestion, but IMHO not worth to ship an update for through the SRU policy.
Instead of a comment change in the old release I'd personally personally think this bug is already good (as it can be found by search engines) - maybe one should write a good askubuntu entry about it?
That would probably be read more often than the comment in the init file?
Opinions?
The newer versions already avoid that by no more being after mounts, only in between network-pre and network.
Wants=network. target network. target pre.target
Before=
After=network-
The subservices (bgpd, ripd, ...) are all integrated after zebra in between the same to network-pre/network and bind start/stop to zebra itself zebra.service target network. target
BindsTo=
Wants=network.
After=zebra.service network-pre.target
Before=
That said the issue you mentioned is fixed in newer releases as you assumed.
So let us look at the older releases.
Changing the dependencies of these releases now - as outlined there are cases that can need that - will be too much regression risk.
Suggesting a comment in the config/init is a nice suggestion, but IMHO not worth to ship an update for through the SRU policy.
Instead of a comment change in the old release I'd personally personally think this bug is already good (as it can be found by search engines) - maybe one should write a good askubuntu entry about it?
That would probably be read more often than the comment in the init file?
Opinions?