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
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.
sh# systemctl cat cups.socket
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)
to comment on this ticket.
Copyright © 2014-2017 Red Hat
2.13.2 — Documentation