sssd.git/src/monitor, branch sssctl

UTIL: Remove signal.h from util/util.h

2017-06-08T15:09:31+00:00

signal.h is not used directly by util/util.h. The header file signal.h
must be included in 19 files and after removing it from util.h it had to be
added only to 12 missing files. And util.util.h is included in 381 files

Reviewed-by: Fabiano Fidêncio

codegen: Remove util.h from generated files

2017-06-08T15:09:13+00:00

Reviewed-by: Fabiano Fidêncio

UTIL: Drop unused error code ERR_MISSING_CONF

2017-05-23T09:36:34+00:00

Reviewed-by: Jakub Hrozek 
Reviewed-by: Pavel Březina

CONFDB: Allow configuring [application] sections as non-POSIX domains

2017-03-30T12:09:10+00:00

Related to:
https://pagure.io/SSSD/sssd/issue/3310

Allows to add a new section:
    [application/$name]

This section internally (on the confdb level) expands to:
    [domain/$name]
    domain_type = application

The reasons to add this new section is two-fold. One, to make the
configuration of application domains more explicit and two, to make it
possible to share configuration between two domains, one POSIX and one
non-POSIX by application domain's inherit_from option:
    [application/$name]
    inherit_from = posix_domain_name

Reviewed-by: Sumit Bose 
Reviewed-by: Pavel Březina

MONITOR: Enable an implicit files domain if one is not configured

2017-02-27T18:14:15+00:00

If SSSD is compiled with --enable-files-domain, the loading of the
domains changes such that:
    * if no domain with id_provider=files exists in the config file, an
      implicit SSSD files domain is added
    * this domain is always first in the list

The administrator is free to create a files domain in the config file
himself and either place it at the end of the list or not enable it at
all.

Resolves:
https://pagure.io/SSSD/sssd/issue/3112

Reviewed-by: Pavel Březina

MONITOR: Don't return an error in case we fail to register a service

2017-02-22T13:03:22+00:00

This behaviour was mistakenly changed by the {dbus,socket}-activation
series and, as it's now, I've noticed the monitor may end up in some
weird state due to this change, where it doesn't stop properly and leave
some defuncts children processes.

Let's change it back to what it was before and avoid possible
regressions (even if no regression where hit yet).

Signed-off-by: Fabiano Fidêncio 

Reviewed-by: Pavel Březina

MONITOR: Use the common inotify code to watch resolv.conf

2017-02-15T13:53:58+00:00

The monitor code used its own inotify callbacks to watch for changes to
resolv.conf. Instead of keeping this duplicated code around, let's use
the shared inotify module that also powers the files provider.

Reviewed-by: Pavel Březina

MONITOR: Remove checks for sssd.conf changes

2017-02-15T13:53:54+00:00

This feature was if-ed out for many years and since it's quite unlikely
we will re-enable the feature in the foreseeable future, let's just
remove this code.

Reviewed-by: Pavel Březina

MONITOR: Don't timeout if using local provider + socket-activated responders

2017-02-10T15:47:47+00:00

When using only the local provider with socket-activated services SSSD
ends up never notifying systemd its startup has been done, as notifying
systemd is done *only* when a service (provider or responder) is started
up, leading SSSD's startup to fail due to a timeout.

So, in order to avoid this situation, let's just notify the startup
earlier in case we have *only* socket-activated services and the *only*
provider set up is the LOCAL one.

Resolves:
https://fedorahosted.org/sssd/ticket/3299

Signed-off-by: Fabiano Fidêncio 

Reviewed-by: Pavel Březina

MONITOR: Wrap up sending sd_notify "ready" into a new function

2017-02-10T15:47:35+00:00

This new function will be used later on in this series as we also will
need to notify systemd that we're up in at least one more scenario (for
now).

Related:
https://fedorahosted.org/sssd/ticket/3299

Signed-off-by: Fabiano Fidêncio 

Reviewed-by: Pavel Březina