URL:
https://github.com/SSSD/sssd/pull/5539
Title: #5539: [WIP] NSS: Clear negative cache when SIGHUP received
alexey-tikhonov commented:
"""
> But I would question "why" the same signal SIGHUP was
re-used both for log rotation and mem-cache clearance. As a result, sss_cache triggers
logs rotation. Is it intentional?
This is a good point, I think it may also contribute to the whole "slow files
provider" issue.
How?
> You don't need to touch permanent entries to resolve this
issue.
Here let me quote @sumit-bose
[
https://github.com/[/issues/4973](https://github.com/SSSD/sssd/issues/4973)]
```
About the tricky part, the memory used by the in-memory tdb is not freed if individual
entries are removed
so you have to close and open the tbd to get back the memory. Now you should not forget
to add
the permanent entries again, but calling sss_ncache_reset_repopulate_permanent() should
be sufficient here.
```
If you don't touch permanent entries then you don't need to add it back again.
If you want to do a full cycle with close/open to partially resolve another ticket
mentioned (about mem leak), then this comment apply. But in your patch you don't do
this.
"""
See the full comment at
https://github.com/SSSD/sssd/pull/5539#issuecomment-802971608