Bug 1024522 - start dirsrv after ntpd
start dirsrv after ntpd
Status: CLOSED WONTFIX
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: 389-ds-base (Show other bugs)
6.4
Unspecified Unspecified
unspecified Severity unspecified
: rc
: ---
Assigned To: Rich Megginson
Sankar Ramalingam
:
Depends On:
Blocks: 1024541 1061410
  Show dependency treegraph
 
Reported: 2013-10-29 16:33 EDT by Nathan Kinder
Modified: 2014-03-03 14:45 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1024541 (view as bug list)
Environment:
Last Closed: 2014-03-03 14:45:50 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)

  None (edit)
Description Nathan Kinder 2013-10-29 16:33:00 EDT
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.

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