Bug 115310 – ldap init script's "reload" function kills slapd/slurpd

Bug 115310 - ldap init script's "reload" function kills slapd/slurpd

Summary:	ldap init script's "reload" function kills slapd/slurpd

Status:	CLOSED RAWHIDE

Aliases:	None

Product:	Red Hat Enterprise Linux 3
Classification:	Red Hat
Component:	openldap (Show other bugs)
Sub Component:
Version:	3.0
Hardware:	All Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Nalin Dahyabhai
QA Contact:	Jay Turner
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2004-02-10 11:22 EST by Christopher C. Weis
Modified:	2015-01-07 19:07 EST (History)
CC List:	1 user (show)

See Also:
Fixed In Version:	2.1.25-4
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2004-02-10 11:41:32 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Christopher C. Weis 2004-02-10 11:22:47 EST

Description of problem:

/etc/init.d/ldap contains the "reload" function, which basically sends
slapd (and slurpd) a SIGHUP.  Instead of reloading the configuration
file, it simply kills slapd (and slurpd).

Version-Release number of selected component (if applicable):
openldap-2.0.27-11

How reproducible:
Always

Steps to Reproduce:
1. "service ldap reload"
2.
3.
  
Actual results:
slapd/slurpd processes no longer exist

Expected results:
slapd/slurpd continue to run, using any new changes in the
configuration files.

Additional info:
"service ldap restart" is a workaround, but it's not very efficient,
especially on large directory servers.

Comment 1 Nalin Dahyabhai 2004-02-10 11:41:32 EST

Reload actually never worked, and can't be done simply.  Removing the
option because it does more harm than good.

Note You need to log in before you can comment on or make changes to this bug.