We should make a change to our initscript to start after ntpd.
1 2 3 4 5
#!/bin/sh # # dirsrv This starts and stops dirsrv # # chkconfig: - 21 79
ntpd
1 2 3 4 5 6
#!/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.
don't forget the dirsrv-snmp etc etc scripts ;)
Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1024522
We will need to see if something similar needs to be done for systemd based platforms.
git patch file (master) 0001-Ticket-47574-start-dirsrv-after-ntpd.patch
In an initscript: {{{
}}} The first number is the start priority, and the second number is the stop priority. In order for dirsrv to start after ntpd, the start priority must be greater than 58, and the stop priority must be less than 74. I suppose using 59 and 73 would be the most logical thing to do.
Replying to [comment:12 rmeggins]:
In an initscript: {{{ chkconfig: - 21 79 }}} The first number is the start priority, and the second number is the stop priority. In order for dirsrv to start after ntpd, the start priority must be greater than 58, and the stop priority must be less than 74. I suppose using 59 and 73 would be the most logical thing to do.
I see. Thanks, Rich! Actually, since this ticket's target milestone is 1.3.3, it looks there's no chance to use initscript. But I thought it'd be a good idea to update the file, as well, just in case we need to backport...
git patch file (master) -- rivised based upon the comments by Rich. 0001-Ticket-47574-start-dirsrv-after-ntpd.2.patch
Reviewed and commented by rmeggins@redhat.com (Thank you, Rich!!)
Pushed to master: 2b7b9cb..fd71c23 master -> master commit fd71c23
Just a remark - starting from RHEL7 ntpd is not the default time sync daemon any more. The new time sync daemon is chronyd.service for systemctl
Metadata Update from @nhosoi: - Issue assigned to nhosoi - Issue set to the milestone: 1.3.3 - 8/14 (August)
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/911
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: Fixed)
Login to comment on this ticket.