URL:
https://github.com/SSSD/sssd/pull/5433
Title: #5433: Only start sssd.service if there's a configuration file present
sergiodj commented:
"""
I'm not sure but this might be a little bit more involved.
Probably there are valid cases when sssd can start despite absence of
`/etc/sssd/sssd.conf`:
* configuration snippets in `conf.d`
* if built with `--enable-files-domain`
(needs to be double-checked)
Ah, fair enough. On Debian/Ubuntu, we explicitly use `--disable-files-domain`. We do
support things in `/etc/sssd/sssd/conf.d/`, though.
I don't have a solution for the former (and haven't tested to see if it's
really the case), but to address the latter we can do something like this in the service
file:
```
ConditionPathExists=|/etc/sssd/sssd.conf
ConditionPathExistsGlob=|/etc/sssd/sssd/conf.d/*
```
I will do some tests and update the PR accordingly.
"""
See the full comment at
https://github.com/SSSD/sssd/pull/5433#issuecomment-748367583