[Leaplist] Name Service Cache Daemon (nscd)

[Bryan J Smith]

Various conditions will always cause issues for nscd.  As Kevin
mentioned, look elsewhere for DNS caching.

As far as NIS, I found the best solution for NIS (other than booting
it) is to replicate the maps (via another protocol) and make every
system it's own slave server, reading it's own local files.  You'd
be surprised how effective of a solution this is.  It is also a good
way to meet compliance (no NIS over the network), while transitioning
to LDAP. It's certainly more manageable than editing local files
and trying to replicate changes between systems. ;)

As far as LDAP, for Fedora-Red Hat (and rebuilds), quite a bit
of knowledge is in Bugzilla when it comes to nscd.  My federal client
is utilizing various LDAP services and using nscd on all systems.
It is still supported by Red Hat as a key component.

--  
Bryan J Smith - mailto:b.j.smith at ieee.org  
http://www.linkedin.com/in/bjsmith
Sent via BlackBerry from T-Mobile  
    

-----Original Message-----
From: Kevin Inscoe <kevin at inscoe.org>
Date: Thu, 7 Jan 2010 11:51:21 
To: This is the Leap Main List<leaplist at leap-cf.org>
Subject: Re: [Leaplist] Name Service Cache Daemon (nscd)

Nothing since they want to use it for LDAP and NIS.

On Thu, Jan 7, 2010 at 11:41 AM, Kevin Korb <kmk at sanitarium.net> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> I have only seen it cause problems as well but I can't say I have any
> proof.
>
> What does it provide that a caching dns server (dnscache) wouldn't provide?
>
> On Thu, 7 Jan 2010 10:21:08 -0500
> Kevin Inscoe <kevin at inscoe.org> wrote:
>> I have a constant battle at work about the nscd daemon. I have
>> consistently had problems with it in both Solaris and RHEL. I am being
>> asked (read semi-forced) to institute it again (I am the one of the
>> Linux build masters for the company) in RHEL 4 and 5 . I would be
>> grateful for any hard evidence documentation from any where to either
>> it's benefits or problems in production environments. Personal
>> anecdotes are also welcome. Yes I have STFG.
>>
>> Regards,
>>
>
>
> - --
> ~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~
>        Kevin Korb                      Phone:    (407) 252-6853
>        Systems Administrator           Internet:
>        FutureQuest, Inc.               Kevin at FutureQuest.net  (work)
>        Orlando, Florida                kmk at sanitarium.net (personal)
>        Web page:                       http://www.sanitarium.net/
>        PGP public key available on web site.
> ~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.11 (GNU/Linux)
>
> iEYEARECAAYFAktGDqcACgkQVKC1jlbQAQcyfQCcCOinHcyIGuFjlRyNwmliOFA4
> cVQAmwc2vzHIvaTjYYiiWzkZ5cVBQ2Gb
> =qxeZ
> -----END PGP SIGNATURE-----
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>
>
>_______________________________________________
> Leaplist mailing list
> Leaplist at leap-cf.org
> http://lists.leap-cf.org/mailman/listinfo/leaplist
>
>



-- 
Kevin P. Inscoe        Amateur Call Sign: KE3VIN
Deltona, FL 32738          28.9497N by 81.1952W
kevin [at] inscoe [dot] org  http://kevininscoe.com

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

_______________________________________________
Leaplist mailing list
Leaplist at leap-cf.org
http://lists.leap-cf.org/mailman/listinfo/leaplist

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.