public inbox for
 help / color / mirror / Atom feed
From: "Lavrentiev, Anton (NIH/NLM/NCBI) [C]" <>
To: Cygwin Patches <>
Subject: RE: [PATCH] CYGWIN: Fix resolver debugging output
Date: Tue, 2 Feb 2021 19:38:58 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

> with some customizations, and not noticed any issues so far. Should I be wary in future?

Have you used the <resolv.h>/<arpa/nameser.h> APIs, or low-level DNS other than with getXbyY(), or maybe debugged DNS?

The changes are not to remove any existing functionality -- I don't see how that was not clear --
but to make it easier to use the API when you have to do a little extra, like seeing the nameserver
IP addresses in a more human-readable form.  But TBH, using native API (in the absence of /etc/resolv.conf,
or by using "options osquery" in it -- but then most of the stuff in that file is just simply ignored, JFYI),
is the best way of dealing with DNS in CYGWIN.  The minires.c implementation is rather simplistic (but it's
good when one needs to stay in full control / observe of what they are doing -- and for me is the development
stage, but I'll drop that and switch back to the OS API once everything is working as it should, for the project
that I'm dealing with right now).

Also, there was at least one bug.

      reply	other threads:[~2021-02-02 19:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-29 19:29 Anton Lavrentiev
2021-02-01 10:34 ` Corinna Vinschen
2021-02-01 14:23   ` Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2021-02-01 15:02     ` Corinna Vinschen
2021-02-01 15:46       ` Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2021-02-01 19:02         ` Corinna Vinschen
2021-02-02 18:02           ` Brian Inglis
2021-02-02 19:38             ` Lavrentiev, Anton (NIH/NLM/NCBI) [C] [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:

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

  git send-email \ \ \ \

* 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).