Bug 1024522

Summary: start dirsrv after ntpd
Product: Red Hat Enterprise Linux 6 Reporter: Nathan Kinder <nkinder>
Component: 389-ds-baseAssignee: Rich Megginson <rmeggins>
Status: CLOSED WONTFIX QA Contact: Sankar Ramalingam <sramling>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.4CC: jgalipea
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1024541 (view as bug list) Environment:
Last Closed: 2014-03-03 19:45:50 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:    
Bug Blocks: 1024541, 1061410    

Description Nathan Kinder 2013-10-29 20:33:00 UTC 
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.