Bug 1024541

Summary: start dirsrv after ntpd
Product: Red Hat Enterprise Linux 7 Reporter: Nathan Kinder <nkinder>
Component: 389-ds-baseAssignee: Rich Megginson <rmeggins>
Status: CLOSED ERRATA QA Contact: Viktor Ashirov <vashirov>
Severity: unspecified Docs Contact:
Priority: low    
Version: 7.0CC: mreynolds, nhosoi, vashirov
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 389-ds-base-1.3.3.1-1.el7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1024522 Environment:
Last Closed: 2015-03-05 09:31:15 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1024522    
Bug Blocks:    
Attachments:
Description Flags
bootchart none

Description Nathan Kinder 2013-10-29 21:47:44 UTC 
+++ This bug was initially created as a clone of Bug #1024522 +++

This bug is created as a clone of upstream ticket:
https://fedorahosted.org/389/ticket/47574

We should make a change to our initscript to start after ntpd.
{{{
#!/bin/sh
#
# dirsrv    This starts and stops dirsrv
#
# chkconfig:   - 21 79
}}}
ntpd
{{{
#!/bin/bash
#
# ntpd          This shell script takes care of starting and stopping
#               ntpd (NTPv4 daemon).
#
# chkconfig: - 58 74
}}}
Would probably make sense to set the start priority to something like 80.
It's unlikely one needs the dirsrv so early at boot time.
Comment 4 Viktor Ashirov 2014-12-26 00:53:46 UTC 
Created attachment 973095 [details]
bootchart
Comment 5 Viktor Ashirov 2014-12-26 00:59:22 UTC 
$ rpm -qa | grep 389
389-ds-base-debuginfo-1.3.3.1-10.el7.x86_64
389-ds-base-1.3.3.1-10.el7.x86_64
389-ds-base-libs-1.3.3.1-10.el7.x86_64

Judging by PID numbers and bootchart, ns-slapd starts after ntpd. Marking as VERIFIED.
Comment 7 errata-xmlrpc 2015-03-05 09:31:15 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHSA-2015-0416.html