On 10/24/12 15:19, Alex Netes wrote:
Hi Bart,
On 16:43 Fri 21 Sep , Bart Van Assche wrote:
"chkconfig $service on" enables a service in the runlevels mentioned
next to "Default-Start" and only in those runlevels.
Signed-off-by: Bart Van Assche <[email protected]>
Cc: Doug Ledford <[email protected]>
---
configure.in | 10 ++++++++++
scripts/opensm.init.in | 4 ++--
scripts/redhat-opensm.init.in | 3 +++
3 files changed, 15 insertions(+), 2 deletions(-)
diff --git a/configure.in b/configure.in
index eb252ff..f660a5b 100644
--- a/configure.in
+++ b/configure.in
@@ -11,6 +11,16 @@ AM_INIT_AUTOMAKE
AC_SUBST(RELEASE, ${RELEASE:-unknown})
AC_SUBST(TARBALL, ${TARBALL:-${PACKAGE}-${VERSION}.tar.gz})
+if { rpm -q sles-release || rpm -q openSUSE-release; } >/dev/null 2>&1; then
+ default_start="2 3 5"
+ default_stop="0 1 4 6"
+else
+ default_start="2 3 4 5"
+ default_stop="0 1 6"
+fi
+AC_SUBST(DEFAULT_START, $default_start)
+AC_SUBST(DEFAULT_STOP, $default_stop)
+
Can you please elaborate more why there is a difference with runlevels
selection between SUSE and RH?
Most services in SLES and openSUSE, including syslog, are enabled in
runlevels 2, 3 and 5 but not in runlevel 4. RHEL systems however follow
the LFS and have services like syslog enabled in runlevels 2, 3, 4 and
5. One of the patches I posted adds $syslog to the list of services that
must be started before opensm is started. If the Default-Start runlevels
specified in /etc/init.d/opensm do not match the runlevels in which
syslog is started then chkconfig prints a warning when enabling the
opensm service. Hence the above code to make the Default-Start runlevels
of opensm match the Default-Start runlevels of syslog.
Bart.
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
