Bug#743504: activemq: Init script returns uncorrect exit code (0) for status command if service is stopped
Baptiste Grenier
baptiste at bapt.name
Thu Apr 3 13:47:38 UTC 2014
Package: activemq
Version: 5.6.0+dfsg-1
Severity: normal
Dear Maintainer,
The activemq init script does return an uncorrect exit code for the status
command when the service is stopped, it returns 0 instead of > 0.
It makes it impossible to managed the sercice using tools such as puppet.
See https://tickets.puppetlabs.com/browse/CPR-17 for some information about this.
Best,
Baptiste
-- System Information:
Debian Release: 7.4
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to fr_FR.UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages activemq depends on:
ii adduser 3.113+nmu3
ii libactivemq-java 5.6.0+dfsg-1
ii openjdk-7-jre-headless [java6-runtime-headless] 7u25-2.3.10-1~deb7u1
activemq recommends no packages.
activemq suggests no packages.
-- no debconf information
More information about the pkg-java-maintainers
mailing list