#3323 The sssd-$RESPONDER.service units should bind to their socket units

Created 6 months ago by sgallagh
Modified a month ago

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.

6 months ago

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.

6 months ago

Metadata Update from @jhrozek:
- Issue set to the milestone: SSSD 1.15.2

6 months ago

Metadata Update from @lslebodn:
- Issue set to the milestone: SSSD 1.15.3 (was: SSSD 1.15.2)

6 months ago

Metadata Update from @jhrozek:
- Issue priority set to: major

4 months ago

Metadata Update from @jhrozek:
- Issue set to the milestone: SSSD 1.15.4 (was: SSSD 1.15.3)

a month ago

Metadata Update from @jhrozek:
- Issue tagged with: PR

Login to comment on this ticket.

cancel