URL:
https://github.com/SSSD/sssd/pull/136
Title: #136: Tlog integration
lslebodn commented:
"""
On (28/04/17 08:11), Nikolai Kondrashov wrote:
Sure, a weak dependency sounds right.
I would not like disabling SSSD or session recording in case tlog is missing.
It is not disabling SSSD; because SSSD will not even start any responder or
back-end :-). And sssd can fail to start even due to other misconfiguration
e.g. wrong permissions on /etc/sssd/sssd.conf ...
If it can be fixed by just installing tlog, then we shouldn't
break SSSD, and let users fix the situation with as little fuss as possible. I.e. without
the need to restart SSSD.
* sssd won't start and log message to syslog that session recording is enabled
(scope != none) and tlog is missing.
* user will try to find a reason why sssd failed to start; check log files
and find out that there is missing binary for tlog shell
* user will install tlog
* start sssd and everything works like a magic :-)
It is just an idea how to simply solve this case. But feel free to use other
way.
"""
See the full comment at
https://github.com/SSSD/sssd/pull/136#issuecomment-298048544