GitHub user TomyLobo opened a pull request:

    https://github.com/apache/activemq/pull/206

    Add missing runlevels to Default-Start

    According to the manual (and the `runlevel` command), Debian starts in 
runlevel 2 by default:
    
https://www.debian.org/doc/manuals/debian-reference/ch03.en.html#_sysv_style_init
    
    So in order for ActiveMQ to start up when a Debian VM starts, you have to 
add it to these runlevels.
    
    Workaround: `insserv -v activemq,start=2`
    
    Side-effects:
    RedHat doesn't use runlevels 2 and 4, so it should be fine:
    
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/3/html/Reference_Guide/s1-boot-init-shutdown-sysv.html
    
    SLES doesn't use runlevel 4, but it does use runlevel 2 for "Local 
multiuser mode without remote network (NFS, etc.)":
    
https://www.suse.com/documentation/sles11/book_sle_admin/data/sec_boot_init.html
    
    So the only side-effect on these systems is that SLES will try to run 
ActiveMQ in Local multiuser mode without remote network (and probably fail).
    I think that is an acceptable side-effect since people booting Debian into 
runlevel 2 is a *lot* more common due to it being the default.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/TomyLobo/activemq patch-1

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/activemq/pull/206.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #206
    
----
commit 7eb9d60c8d203829b020025b20411628a20ab780
Author: TomyLobo <[email protected]>
Date:   2016-10-25T09:03:44Z

    Add missing runlevels to Default-Start
    
    Debian starts in runlevel 2 by default.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to