public inbox for libc-help@sourceware.org
 help / color / mirror / Atom feed
From: "Carlos O'Donell" <carlos@systemhalted.org>
To: 이병욱 <nimdrak@naver.com>
Cc: libc-help <libc-help@sourceware.org>
Subject: Re: How to compile and use 'nscd'
Date: Sun, 24 Jul 2022 09:50:37 -0400	[thread overview]
Message-ID: <CAE2sS1hAMOL1itzzTOZMdNcTiFeLW=dNBdsafinkRPiAMm2emg@mail.gmail.com> (raw)
In-Reply-To: <268721506430b9d1fa3e1725d230e59b@cmweb01.nm.nfra.io>

On Sun, Jul 24, 2022 at 3:57 AM 이병욱 via Libc-help
<libc-help@sourceware.org> wrote:
>
> I found nscd's dafault ttl should be 15 seconds
>
> because CACHE_PRUNE_INTERVAL is declared as 15.
>
> But it seems hard to modify it and compile nscd and use the customed nscd in my Centos 7.9.
>
> I want to see how nscd works when CACHE_PRUNE_INTERVAL is 1 because I try to use DNS round robin at below environments.
>
> - dns A record www.server.com with 10.1.1.1, 10.1.1.2 with dns ttl 1 seconds.
> - client server with customed nscd, send a request to www.server.com
> - two backend server indicated by 10.1.1.1, 10.1.1.2
>
> Is it possible to use the customed nscd?

It is technically possible to use a customized nscd. However, using a
customized nscd can impact your support through your distribution.

The design goals behind nscd are to cache results locally in as simple
a manner as possible.

The internal hosts cache in nscd is aware of TTL, but the CentOS 7 era
nscd may still have some issues regarding refreshing values based on
TTL.

The value of CACHE_PRUNE_INTERVAL is defined in nscd/nscd.h, and
rebuilding an nscd for your distribution is most easily accomplished
by rebuilding the distribution rpm with a patch added.

The CACHE_PRUNE_INTERVAL drives the loop that prunes the cache, but
other effects prune the cache also, which for the hosts cache should
include the entries ttl.

I suggest evaluating other caching options before changing nscd
though, and you may find it beneficial to look at sssd.

Cheers,
Carlos.

  reply	other threads:[~2022-07-24 13:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-24  7:57 이병욱
2022-07-24 13:50 ` Carlos O'Donell [this message]
2022-07-24 14:15   ` 이병욱
2022-07-29 16:41     ` Carlos O'Donell
2022-07-31  9:18       ` 이병욱
2022-07-31  9:20       ` 이병욱

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAE2sS1hAMOL1itzzTOZMdNcTiFeLW=dNBdsafinkRPiAMm2emg@mail.gmail.com' \
    --to=carlos@systemhalted.org \
    --cc=libc-help@sourceware.org \
    --cc=nimdrak@naver.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).