public inbox for libc-hacker@sourceware.org
 help / color / mirror / Atom feed
From: hjl@valinux.com (H.J. Lu)
To: drepper@cygnus.com
Cc: libc-hacker@sourceware.cygnus.com (GNU C Library)
Subject: Re: A patch for libresolv
Date: Mon, 11 Oct 1999 15:00:00 -0000	[thread overview]
Message-ID: <19991011215952.E1D603FC1@valinux.com> (raw)
In-Reply-To: <m3670dbmiq.fsf@localhost.localnet>

> 
> hjl@valinux.com (H.J. Lu) writes:
> 
> > There are many options in libresolve. However, there are no codes to
> > set them. Here is a patch to handle options for libresolve.
> 
> Where is the existing practice for this?  We cannot simply invent this
> because at least I don't understand the code completely.
> 
> Just a brief look already showed a problem.  The RES_IGNTC flag is
> used in the bind 8 code internally (res_sendsigned.c).  It is

Then take it out from my patch.

> obviously not meant to be set by the user.  Probably this is correct
> for the rest as well.
> 
> I'll compare the res_init code in glibc and in bind 8 and make
> whatever changes this suggests.  But simply extending the option
> format is not correct.
> 

There are many RES_XXXXX macros but they are not settable by users.
I have a need to set RES_INSECURE1/RES_INSECURE2. I don't want to
recompile glibc to do it. 


-- 
H.J. Lu (hjl@gnu.org)

  reply	other threads:[~1999-10-11 15:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-10-05 18:27 H.J. Lu
1999-10-11 14:47 ` Ulrich Drepper
1999-10-11 15:00   ` H.J. Lu [this message]
1999-10-11 15:07     ` Ulrich Drepper
1999-10-11 15:11       ` H.J. Lu
1999-10-11 17:20         ` Geoff Keating
1999-10-11 17:26           ` H.J. Lu
1999-10-11 17:37             ` Geoff Keating
1999-10-11 17:56               ` H.J. Lu

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=19991011215952.E1D603FC1@valinux.com \
    --to=hjl@valinux.com \
    --cc=drepper@cygnus.com \
    --cc=libc-hacker@sourceware.cygnus.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).