Discrepancy in use of 'entry_cache_timeout' in 'nss' section?

[sssd-bot]

Cloned from Pagure issue: https://pagure.io/SSSD/sssd/issue/3893

• Created at 2018-12-04 19:45:54 by numbernine9999
• Closed at 2018-12-06 21:59:06 as Invalid
• Assigned to nobody

---

Hello!

I am using SSSD 1.16.0-19 and running into an issue between what the sssd.conf man page says and the warnings that sssd is reporting on startup.

I am attempting to use the entry_cache_timeout configuration option inside of an [nss] service section inside my sssd.conf file. According to this version of the man page, this value is supported here. When I start sssd using this field inside of the [nss] section, however, I get a warning in my sssd.log like the following:

(Tue Dec  4 12:07:49:318557 [sssd] [sss_ini_call_validators] (0x0020): [rule/allowed_nss_options]: Attribute 'entry_cache_timeout' is not allowed in section 'nss'. Check for typos.

Interestingly, if I look at the validators here , I don't see entry_cache_timeout as a field that is listed in the [nss] section as valid.

Would someone be able to clarify if this value is supported or not? Thanks. :-)

Comments

---

Comment from jhrozek at 2018-12-04 22:17:25

This is a domain side option only -- the domain saves the entry so it needs to decide how long is the entry lifetime. Looking at sssd.conf man page on my system, the entry is listed under "domain sections". Maybe the man page is confusing, but what leads you to considering the option as nss-section one?

---

Comment from numbernine9999 at 2018-12-06 21:26:50

@jhrozek Thanks for getting back to me! Evidently, I am blind. I'm not sure how many times I read the man page, but I misread enum_cache_timeout as entry_cache_timeout in the NSS configuration options section; it probably didn't help that the configuration option immediately below that is entry_cache_timeout_percentage!

It appears everything is fine; I just need my eyes checked or try to modify sssd.conf when tired. :-)

---

Comment from jhrozek at 2018-12-06 21:59:07

np, glad it works

---

Comment from jhrozek at 2018-12-06 21:59:07

Metadata Update from @jhrozek:

• Issue close_status updated to: Invalid
• Issue status updated to: Closed (was: Open)