Ticket was cloned from Red Hat Bugzilla (product Fedora): Bug 1114935
Description of problem: After successfully running setup-ds.pl and rebooting, the directory server is not running after boot. One would expect the service to be enabled by default or at least a command line switch for setup-ds.pl provided for that. Version-Release number of selected component (if applicable): Fedora 20
The preferred solution would be to add a command line switch. For example, setup-ds.pl -b/--boot - start instance at boot time. We cannot possibly support all platforms, but we could at least say "Error: -b/--boot switch not supported on your platform %s. Please consult your system documentation about how to enable instance %s to start at boot time"
I think we should target systemd systems initially, then service/sysvinit systems.
This is a duplicate of ticket #47616.
Metadata Update from @edewata: - Issue set to the milestone: FUTURE
Metadata Update from @firstyear: - Custom field reviewstatus adjusted to new - Issue close_status updated to: duplicate - Issue status updated to: Closed (was: Open)
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/1168
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: duplicate)