The newer versions already avoid that by no more being after mounts,
only in between network-pre and network.
Wants=network.target
Before=network.target
After=network-pre.target
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?
** Also affects: quagga (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: quagga (Ubuntu)
Status: Incomplete => Fix Released
** Changed in: quagga (Ubuntu Trusty)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1777348
Title:
init.d/quagga has erroneous $remote_fs in LSB headers
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/quagga/+bug/1777348/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
