ganglia/monitor-core — Issue #20: Suse Startup Files broken
Author: knobi
Created: 2012-03-02 11:38:43+00:00
State: open

For both gmetad and gmond you find the following code in the Suse specific startup files:

gmetad
----------

# Determine the base and follow a runlevel link name.
base=${0##*/}
link=${base#*[SK][0-9][0-9]}

# Force execution if not called by a runlevel directory.
test $link = $base && START_GMETAD=yes
test "$START_GMETAD" = yes || exit 0

gmond
---------

# Determine the base and follow a runlevel link name.
base=${0##*/}
link=${base#*[SK][0-9][0-9]}

# Force execution if not called by a runlevel directory.
test $link = $base && START_GMOND=yes
test "$START_GMOND" = yes || exit 0

The problem is that START_GMOND/START_GMETAD are never even tried to be defined before that code. As a result, that code prevents startup when called out of a runlevel directory.