summaryrefslogtreecommitdiffstats
path: root/configure.ac
diff options
context:
space:
mode:
authorOndrej Kos <okos@redhat.com>2013-06-19 14:05:00 +0200
committerJakub Hrozek <jhrozek@redhat.com>2013-06-25 10:42:36 +0200
commit1554077521ea202bc886d6483b72e5ebdc10c520 (patch)
treedae1a3e2d542da0cb0a1c10965b2d7fac7505fbf /configure.ac
parent8adef6fcff7db7b40efa242b147641ffa2981fb0 (diff)
downloadsssd-1554077521ea202bc886d6483b72e5ebdc10c520.tar.gz
sssd-1554077521ea202bc886d6483b72e5ebdc10c520.tar.xz
sssd-1554077521ea202bc886d6483b72e5ebdc10c520.zip
exit original process after sssd is initialized
https://fedorahosted.org/sssd/ticket/1357 Neither systemd or our init script use pid file as a notification that sssd is finished initializing. They will continue starting up next service right after the original (not daemonized) sssd process is terminated. If any of the responders fail to start, we will never terminate the original process via signal and "service sssd start" will hang. Thus we take this as an error and terminate the daemon with a non-zero value. This will also terminate the original process and init script or systemd will print failure.
Diffstat (limited to 'configure.ac')
0 files changed, 0 insertions, 0 deletions