389-ds-base

#48030 spec file should run "systemctl stop" against each running instance instead of dirsrv.target
Closed: wontfix Opened by nhosoi.

Closed: wontfix
Reopen Issue

https://fedorahosted.org/freeipa/ticket/4709#comment:6
by pviktori
Hm, it turns out systemctl start dirsrv@$INST.service waits until the service is started, systemctl stop dirsrv@$INST.service waits until it's down (i.e. the process exits), systemctl start dirsrv.target waits until all the "wanted" services are started, but systemctl stop dirsrv.target returns immediately.

Actually, a patch was provided by Ludwig. (Thank you!!)

Pushed to master:
b43e899..24c303d master -> master
commit 24c303d3e6c91358fc645268d582144f377e3902

Pushed to 389-ds-base-1.3.3:
74834a2..79a8898 389-ds-base-1.3.3 -> 389-ds-base-1.3.3
commit 79a889882ae6ec57dbc2ffa5aeeac648ca045ec3

Metadata Update from @nhosoi:
- Issue assigned to nhosoi
- Issue set to the milestone: 1.3.3.9

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/1361

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: Fixed)
Metadata
None
None
None
Normal
ack
IPA
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.