Project

General

Profile

Actions

Bug #5368

closed

SLES init script strangeness

Added by Florian Heigl over 9 years ago. Updated about 7 years ago.

Status:
Rejected
Priority:
2
Assignee:
-
Category:
System integration
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Fix check:
Regression:

Description

Hi,

on the following OS I see a funny behaviour:
rudders1:/var/log # cat /etc/SuSE-release
SUSE Linux Enterprise Server 11 (x86_64)
VERSION = 11
PATCHLEVEL = 3

rudders1:/var/log # chkconfig rudder-slapd on
insserv: Service syslog is missed in the runlevels 4 to use service rudder-slapd

Syslog isn't installed since I added this package:
rudders1:/var/log # rpm -aq | grep -i rsyslog
rsyslog-module-pgsql-5.10.1-0.7.49
rsyslog-5.10.1-0.7.49

It seems the system used the original SLES rsyslog package.

Package is installed:
rudders1:/var/log # chkconfig --list | grep -e syslog -e rudder
earlysyslog 0:off 1:off 2:on 3:on 4:off 5:on 6:off
rudder-agent 0:off 1:off 2:off 3:off 4:off 5:off 6:off
rudder-jetty 0:off 1:off 2:off 3:off 4:off 5:off 6:off
rudder-server-root 0:off 1:off 2:off 3:off 4:off 5:off 6:off
rudder-slapd 0:off 1:off 2:on 3:on 4:on 5:on 6:off
syslog 0:off 1:off 2:on 3:on 4:off 5:on 6:off

My only guess is the following:
rudder-slapd:
  1. Required-Start: $remote_fs $syslog
  2. Required-Stop: $remote_fs $syslog
vs.
syslog:
  1. Provides: syslog
  2. Required-Start:
  3. Should-Start: earlysyslog network
  4. Required-Stop:

I'm no linux init guru, but is it because of the $syslog vs. syslog difference?

Actions

Also available in: Atom PDF