https://bugzilla.redhat.com/show_bug.cgi?id=825871 (Fedora)
The 'service' binary is intended to work as a backwards-compatibility wrapper around systemd. However, 'service start dirsrv' no longer works, because you must start dirsrv using 'systemctl start dirsrv.target', not 'systemctl start dirsrv.service'. The latter fails with "No such file or directory."
service start dirsrv should fail, but not silently - we should redirect users of service to use systemctl instead.
set default ticket origin to Community
Added initial screened field value.
"service stop dirsrv failing silently" was fixed by ticket 457. Due to the nature of the systemd wrappers, we can not control how "service" redirects to systemctl.
The 389-ds release notes have been updated with the proper starting/stopping command.
Metadata Update from @mreynolds: - Issue assigned to mreynolds - Issue set to the milestone: 1.3.0
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/423
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.