Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

spec file should run "systemctl stop" against each running instance instead of dirsrv.target #1361

Closed
389-ds-bot opened this issue Sep 12, 2020 · 3 comments
Labels
closed: fixed Migration flag - Issue
Milestone

Comments

@389-ds-bot
Copy link

Cloned from Pagure issue: https://pagure.io/389-ds-base/issue/48030


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.

@389-ds-bot 389-ds-bot added the closed: fixed Migration flag - Issue label Sep 12, 2020
@389-ds-bot 389-ds-bot added this to the 1.3.3.9 milestone Sep 12, 2020
@389-ds-bot
Copy link
Author

@389-ds-bot
Copy link
Author

Comment from nhosoi (@nhosoi) at 2015-02-27 00:51:51

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

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

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

@389-ds-bot
Copy link
Author

Comment from nhosoi (@nhosoi) at 2017-02-11 23:12:35

Metadata Update from @nhosoi:

  • Issue assigned to nhosoi
  • Issue set to the milestone: 1.3.3.9

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed: fixed Migration flag - Issue
Projects
None yet
Development

No branches or pull requests

1 participant