public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "benchan at chromium dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug nscd/13696] New: Add a --disable-nscd option to configure for disabling nscd implementation in glibc functions
Date: Wed, 15 Feb 2012 23:24:00 -0000 [thread overview]
Message-ID: <bug-13696-131@http.sourceware.org/bugzilla/> (raw)
http://sourceware.org/bugzilla/show_bug.cgi?id=13696
Bug #: 13696
Summary: Add a --disable-nscd option to configure for disabling
nscd implementation in glibc functions
Product: glibc
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: nscd
AssignedTo: drepper.fsp@gmail.com
ReportedBy: benchan@chromium.org
Classification: Unclassified
Created attachment 6214
--> http://sourceware.org/bugzilla/attachment.cgi?id=6214
Patch to add --disable-nscd to configure
Background
----------
Although the nscd client code can fall back when it fails to contact the nscd
server, we may sometimes need to avoid that from happening (e.g. we need to
disallow the "socket" system call in a sandboxed environment) if we know that
no nscd server is enabled on a target system. Thus, we need to compile glibc
without using the nscd implementation in its functions.
Problem
-------
The following glibc Makefiles currently hardcode -DUSE_NSCD=1 to use the nscd
implementation for certain glibc functions, which makes it inconvenient to
disable the nscd implementation.
grp/Makefile
inet/Makefile
posix/Makefile
pwd/Makefile
Proposed Solution
-----------------
It would be nicer if we have a --disable-nscd option in configure to control
whether USE_NSCD should be defined. The attached patch implements the proposed
changes on top of the current glibc master branch.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2012-02-15 23:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-15 23:24 benchan at chromium dot org [this message]
2012-02-16 17:40 ` [Bug nscd/13696] " ppluzhnikov at google dot com
2012-02-17 23:37 ` vapier at gentoo dot org
2012-03-07 9:18 ` drepper.fsp at gmail dot com
2012-03-07 13:25 ` vapier at gentoo dot org
2012-08-22 20:42 ` roland at gnu dot org
2014-06-26 15:28 ` fweimer at redhat dot com
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=bug-13696-131@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sources.redhat.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).