summaryrefslogtreecommitdiffstats
path: root/configure.ac
diff options
context:
space:
mode:
authorFabiano Fidêncio <fidencio@redhat.com>2016-11-17 01:03:13 +0100
committerLukas Slebodnik <lslebodn@redhat.com>2017-01-23 18:46:37 +0100
commitf37e795cd16310759dc9741c1ab1323b287a9101 (patch)
treeac767be2413917d0a8bcd4514527660650a80149 /configure.ac
parentb33c275ebac86695f7a2fa866e5766d469e2c578 (diff)
downloadsssd-f37e795cd16310759dc9741c1ab1323b287a9101.tar.gz
sssd-f37e795cd16310759dc9741c1ab1323b287a9101.tar.xz
sssd-f37e795cd16310759dc9741c1ab1323b287a9101.zip
SUDO: Make Sudo responder socket-activatable
As part of the effort of making all responder socket-activatable, let's make Sudo responder ready for this by providing its systemd's units. In case the administrators want to use Sudo responder taking advantage of socket-activation they will need to enable sssd-sudo.socket and after a restart of the sssd service, the Sudo socket will be ready waiting for any activity in order to start the Sudo responder. Also, the Sudo responder must be removed from the services line on sssd.conf. The Sudo responder service is binded to the SSSD service, which means that the responder will be restarted in case SSSD is restarted and shutdown in case SSSD is shutdown/crashes. Related: https://fedorahosted.org/sssd/ticket/2243 Signed-off-by: Fabiano Fidêncio <fidencio@redhat.com> Reviewed-by: Pavel Březina <pbrezina@redhat.com> Reviewed-by: Jakub Hrozek <jhrozek@redhat.com> Reviewed-by: Lukáš Slebodník <lslebodn@redhat.com>
Diffstat (limited to 'configure.ac')
0 files changed, 0 insertions, 0 deletions