From: rdkehn at yahoo.com <rdkehn@yahoo.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v6] package/unscd: new package
Date: Wed, 2 Dec 2015 07:20:31 -0600 [thread overview]
Message-ID: <20151202132031.GB547@dkarchlinux64.currentcomm.com> (raw)
In-Reply-To: <565E130B.7090201@mind.be>
Hi Arnout, Thomas:
On Tue, Dec 01, 2015 at 10:37:15PM +0100, Arnout Vandecappelle wrote:
> Hi Doug,
>
> Even though it's already v6 I still have some comments :-(
>
> On 01-12-15 16:15, Doug Kehn wrote:
> > A daemon which handles passwd, group and host lookups for running
> > programs and caches the results for the next query. You only need this
> > package if you are using slow Name Services like LDAP, NIS or NIS+.
> >
> > This particular NSCD is a complete rewrite of the GNU glibc nscd which
> > is a single threaded server process which offloads all NSS lookups to
> > worker children; cache hits are handled by the parent, and only cache
> > misses start worker children, making the parent immune to resource
> > leaks, hangs, and crashes in NSS libraries.
> >
> > It should mostly be a drop-in replacement for existing installs using
> > nscd.
>
> This explanation is not really relevant for the commit log. Just keep the first
> sentence. All this text should be present in the package help text, however.
>
> It would be good however to explain in the commit log that glibc's nscd is not
> installed by buildroot at the moment, and why it only works with glibc.
>
I'm not sure if unscd, by itself, only works with glibc. Associated
packages that benefit from unscd require glibc. My system is glibc
based so I know this works. I'm not sure about other c-libs.
What is your suggestion here?
Regards,
...doug
prev parent reply other threads:[~2015-12-02 13:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-01 15:15 [Buildroot] [PATCH v6] package/unscd: new package Doug Kehn
2015-12-01 21:37 ` Arnout Vandecappelle
2015-12-01 21:45 ` Thomas Petazzoni
2015-12-02 13:00 ` rdkehn at yahoo.com
2015-12-02 13:20 ` rdkehn at yahoo.com [this message]
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=20151202132031.GB547@dkarchlinux64.currentcomm.com \
--to=rdkehn@yahoo.com \
--cc=buildroot@busybox.net \
/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