Learn more about these different git repos.
Other Git URLs
If a socket-activated responder is running and an administrator calls systemctl stop sssd-foo.socket, the sssd-foo.service remains running, which would be unexpected. This can be fixed by adding BindsTo=sssd-foo.socket to the sssd-foo.service unit files in the [Unit] section.
systemctl stop sssd-foo.socket
sssd-foo.service
BindsTo=sssd-foo.socket
[Unit]
PR: https://github.com/SSSD/sssd/pull/183
Metadata Update from @fidencio: - Issue assigned to fidencio
@sgallagh I would close this ticket as won't fix.
Neither of socket activated services on my system stop service together with stopping socket.
e.g.
sh# systemctl cat cups.socket # /usr/lib/systemd/system/cups.socket [Unit] Description=CUPS Scheduler PartOf=org.cups.cupsd.service [Socket] ListenStream=/var/run/cups/cups.sock [Install] WantedBy=sockets.target
While having it doesn't hurt, I'd say keeping up with the other services are doing is the best thing to do.
By stopping the socket, the service does still keep working, so I'd say it's fine as it is right now.
Metadata Update from @jhrozek: - Issue set to the milestone: SSSD 1.15.2
Metadata Update from @lslebodn: - Issue set to the milestone: SSSD 1.15.3 (was: SSSD 1.15.2)
Metadata Update from @jhrozek: - Issue priority set to: major
Metadata Update from @jhrozek: - Issue set to the milestone: SSSD 1.15.4 (was: SSSD 1.15.3)
Metadata Update from @jhrozek: - Issue tagged with: PR
Since the PR was moved to 2.0, let's move this ticket there as well.
Metadata Update from @jhrozek: - Issue set to the milestone: SSSD 2.0 (was: SSSD 1.15.4)
Metadata Update from @jhrozek: - Issue set to the milestone: SSSD 2.1 (was: SSSD 2.0)
Metadata Update from @fidencio: - Assignee reset
Metadata Update from @jhrozek: - Issue set to the milestone: SSSD 2.2 (was: SSSD 2.1)
Metadata Update from @jhrozek: - Issue set to the milestone: SSSD 2.3 (was: SSSD 2.2)
Metadata Update from @thalman: - Issue tagged with: Canditate to close
Thank you for taking time to submit this request for SSSD. Unfortunately this issue was not given priority and the team lacks the capacity to work on it at this time.
Given that we are unable to fulfill this request I am closing the issue as wontfix.
If the issue still persist on recent SSSD you can request re-consideration of this decision by reopening this issue. Please provide additional technical details about its importance to you.
Thank you for understanding.
Metadata Update from @pbrezina: - Issue close_status updated to: wontfix - Issue status updated to: Closed (was: Open)
SSSD is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in SSSD's github repository.
This issue has been cloned to Github and is available here: - https://github.com/SSSD/sssd/issues/4355
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.
Login to comment on this ticket.