sssd.git/src/util/server.c, branch 1.9.2-35

SERVER: Check the return value of waitpid

2012-11-19T13:36:12+00:00

We should at least print an error message and error out if waitpid()
fails.

https://fedorahosted.org/sssd/ticket/1651

exit original process after sssd is initialized

2012-11-06T20:23:46+00:00

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.

fix indendation, coding style and debug levels in server.c

2012-11-06T20:23:34+00:00

Move some debug lines to new debug log levels

2012-06-20T11:41:04+00:00

 * These are common lines of debug output when starting
   up sssd

https://bugzilla.redhat.com/show_bug.cgi?id=811113

SERVER: use the correct return code of sss_atomic_write_s

2012-05-02T12:10:16+00:00

Convert read and write operations to sss_atomic_read

2012-04-20T14:55:14+00:00

https://fedorahosted.org/sssd/ticket/1209

Don't give memory context in confdb where not needed

2012-02-22T02:28:49+00:00

Fix invalid index in pidfile()

2012-01-21T17:47:57+00:00

If we hit the "read too much, this should never happen" line, we
would write a NULL-terminator past the end of the static buffer.

Coverity 12472

Reorder pidfile() function to guarantee NULL-termination

2011-12-19T16:38:35+00:00

Coverity 12400

DEBUG timestamps offer higher precision

2011-09-08T19:29:42+00:00

https://fedorahosted.org/sssd/ticket/956

Added: --debug-microseconds=0/1
Added: debug_microseconds to sssd.conf