Summary: | pw(8) does not interact with nscd(8) | ||||||
---|---|---|---|---|---|---|---|
Product: | Base System | Reporter: | Sven Berkvens-Matthijsse <sven> | ||||
Component: | bin | Assignee: | Allan Jude <allanjude> | ||||
Status: | Closed Overcome By Events | ||||||
Severity: | Affects Only Me | CC: | amutu, feld | ||||
Priority: | Normal | ||||||
Version: | 7.0-PRERELEASE | ||||||
Hardware: | Any | ||||||
OS: | Any | ||||||
Attachments: |
|
Description
Sven Berkvens-Matthijsse
2008-01-15 19:20:01 UTC
How about the following workaround? assigning to Allan as we chatted about this at vBSDCon 2015 I think the negative-confidence-threshold configuration is introduced to solve problems like this. from the man page: negative-confidence-threshold [cachename] [value] The number of times a query must have failed before the cache accepts that the element can not be found. At the default value of 1 each negative query result is cached and immediately returned from the cache on further queries. Higher numbers cause queries to be retried at the configured data sources the given number of times, before the negative result is returned from the cache on further queries. This allows to probe for the existence of an entry, and then to create it if it did not exist, without the negative probe result preventing access to the new entry for the duration of the negative TTL. batch change: For bugs that match the following - Status Is In progress AND - Untouched since 2018-01-01. AND - Affects Base System OR Documentation DO: Reset to open status. Note: I did a quick pass but if you are getting this email it might be worthwhile to double check to see if this bug ought to be closed. nscd now supports a negative-confidence-threshold and the negative cache entries properly timeout, so this is less of an issue now. |