Start consul service on runlevel 2 in sysvinit

[ghost]

Current LSB header of sysvinit script defines consul service to start on runlevel 3.

Default runlevel in Debian is 2 - https://wiki.debian.org/RunLevel, so it mean that when Debian based host is restarted, then consul service is not started.

To fix this issue I have update LSB header in sysvinit script so now consul service will be launched on runlevel 2.

[codecov-io]

Current coverage is 57.80%

No coverage report found for master at 2876c5e.

Powered by Codecov. Last updated by 2876c5e...be955f0

[johnbellone]

The LSB second runlevel does not have network interfaces up, correct?

[MichaelKueller]

Yes it does. In debian and ubuntu it is the standard runlevel and defined as the "Full multi user mode".
Look here: https://debian-administration.org/article/212/An_introduction_to_run-levels

[johnbellone]

@ZbigniewZabost-zanox you are saying that debian based systems don't get to run level 3?

I don't really have a problem changing this but I want to make sure that we're not going to prematurely start the service when networking is not available.

[MichaelKueller]

Debian based systems by default don't make a difference between runlevels 2 to 5. Therefor a standard debian installation does not get to run level 3. (Zbigniew is my co-worker, we work on this together)

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.