diff options
| author | Pavel Březina <pbrezina@redhat.com> | 2012-10-18 10:16:06 +0200 |
|---|---|---|
| committer | Jakub Hrozek <jhrozek@redhat.com> | 2012-11-06 21:23:46 +0100 |
| commit | 0030538a4559ca15ce6d85e59d3ae8db2ccb79c6 (patch) | |
| tree | 1a1be981c700cc720887080e22acb8cb25c7b9c2 /contrib | |
| parent | 939f4101c7a0b27133dd79aeb79032cb58307b21 (diff) | |
| download | sssd-0030538a4559ca15ce6d85e59d3ae8db2ccb79c6.tar.gz sssd-0030538a4559ca15ce6d85e59d3ae8db2ccb79c6.tar.xz sssd-0030538a4559ca15ce6d85e59d3ae8db2ccb79c6.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 'contrib')
0 files changed, 0 insertions, 0 deletions