hi
nscd-2.5-123.el5_11.1
when execute "id xxx" RH 5.9 I get "No such user", for other users there is no problem.
when I stop "nscd" , "id xxx" works fine.
So I try to tune nscd.conf by increase the "suggested size" from 211 to 10657 , restart the service , but "nscd -g" still show 211, not the new values.
why, please help.
nscd -g: passwd cache:
yes cache is enabled yes cache is persistent yes cache is shared 211 suggested size 216064 total data pool size 12008 used data pool size 600 seconds time to live for positive entries 20 seconds time to live for negative entries 37220499 cache hits on positive entries 52651 cache hits on negative entries 281512 cache misses on positive entries 47695 cache misses on negative entries 99% cache hit rate 130 current number of cached values 291 maximum number of cached values 9 maximum chain length searched 0 number of delays on rdlock 3 number of delays on wrlock 0 memory allocations failed yes check /etc/passwd for changes
grep -v "#" /etc/nscd.conf
server-user nscd debug-level 0 paranoia no enable-cache passwd yes positive-time-to-live passwd 600 negative-time-to-live passwd 20 suggested-size passwd 10657 check-files passwd yes persistent passwd yes shared passwd yes max-db-size passwd 33554432 auto-propagate passwd yes enable-cache group yes positive-time-to-live group 3600 negative-time-to-live group 60 suggested-size group 10657 check-files group yes persistent group yes shared group yes max-db-size group 33554432 auto-propagate group yes enable-cache hosts yes positive-time-to-live hosts 3600 negative-time-to-live hosts 20 suggested-size hosts 10657 check-files hosts yes persistent hosts yes shared hosts yes max-db-size hosts 33554432
br van12
This isn't a 389 issue.
Metadata Update from @rmeggins: - Issue set to the milestone: N/A
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/1905
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: Invalid)
Login to comment on this ticket.