Currently the slapd instance is started immediately after creation. However, after machine reboot it has to be started manually unless the admin manually configured it to start automatically:
http://directory.fedoraproject.org/wiki/Howto:systemd#How_do_I_make_it_start_at_boot_time.3F
It might be better for setup-ds.pl to configure slapd to start automatically by default since usually other applications depend on the service.
attachment 0001-Ticket-47616-Enabling-auto-start-by-default.patch
I do not think we should auto start by default. That is a big change to the existing setup. We don't have anyone else asking for this feature. What is the reason for needing to add auto start to setup?
I don't know if any other server does this.
If we are going to support autostart, we should have a new configuration option to do this e.g. in the setup .inf file:
[slapd] autostart=1 ... [admin] autostart=1
The default would be autostart=0 (no autostart).
Note that we would need to support this in admin server too, although we could do that in a separate ticket.
Also note that this feature is platform specific e.g. on systemd platforms, you use systemctl enable/disable. On other platforms you may have to use "chkconfig". On other platforms, yet other commands. We need some way to be able to figure out, or specify at configure time, the system commands to use to enable/disable auto start.
We are going to close this as "won't fix". Configuring "auto start" is more of a system administrator task(that is platform specific), and not really the responsibility of the server software itself.
Ticket #47837 is a duplicate of this ticket.
Metadata Update from @edewata: - Issue assigned to mreynolds - Issue set to the milestone: N/A
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/953
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: Invalid)
Login to comment on this ticket.