Red Hat Bugzilla – Bug 1024541
start dirsrv after ntpd
Last modified: 2015-03-05 04:31:15 EST
+++ 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.
Created attachment 973095 [details] bootchart
$ 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.
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