summaryrefslogtreecommitdiffstats
path: root/src/util/util.h
diff options
context:
space:
mode:
authorPavel Březina <pbrezina@redhat.com>2012-10-18 10:16:06 +0200
committerJakub Hrozek <jhrozek@redhat.com>2012-11-06 21:23:46 +0100
commit0030538a4559ca15ce6d85e59d3ae8db2ccb79c6 (patch)
tree1a1be981c700cc720887080e22acb8cb25c7b9c2 /src/util/util.h
parent939f4101c7a0b27133dd79aeb79032cb58307b21 (diff)
downloadsssd-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 'src/util/util.h')
-rw-r--r--src/util/util.h1
1 files changed, 1 insertions, 0 deletions
diff --git a/src/util/util.h b/src/util/util.h
index e0f153f26..e50b4f54b 100644
--- a/src/util/util.h
+++ b/src/util/util.h
@@ -359,6 +359,7 @@ void sss_log(int priority, const char *format, ...);
struct main_context {
struct tevent_context *event_ctx;
struct confdb_ctx *confdb_ctx;
+ pid_t parent_pid;
};
int die_if_parent_died(void);