----- Forwarded message from "Pierre A. Humblet" ----- > Date: Thu, 16 Sep 2010 12:43:33 -0400 > From: "Pierre A. Humblet" > Subject: Fw: res_send() doesn't work with osquery enabled > To: Corinna Vinschen <cori...@vinschen.de> > > Corinna, > > this has not made it to the list so far, not sure why. > > I am leaving on a trip and don't have time to investigate, > so sending it straight to you. > > Pierre > **************************************************** > ----- Original Message ----- > From: "Pierre A. Humblet" > To: cygwin-patches > Sent: Thursday, September 16, 2010 9:52 > Subject: Re: res_send() doesn't work with osquery enabled > > > | ----- Original Message ----- > | From: "Corinna Vinschen" > | To: cygwin-patches > | Sent: Friday, September 10, 2010 5:22 > | > | > || Pierre? Ping? > || > | > | Corinna, > | > | Sorry, an earlier answer was rejected due to inappropriate subject. > | > | After thinking about it, I don't like mixing calls to the Windows resolver > | for res_query and contacting DNS servers directly with res_send, > | as proposed. So I have a patch where res_send also uses the Windows > | resolver. > | > | Unfortunately although I can build cygwin1.dll fine, it's broken, > | something to do with a NULL stdout (this is from /bin/date) > | 1 thread 2588.0x4c0 fputc (ch=10, file=0x0) > | at ../../../../../src/newlib/libc/stdio/fputc.c:101 > | > | Not sure what to do, I already did make clean for cygwin. > | > | Also minires used to come with a README explaining the effect of > | an optional /etc/resolv.conf (e.g. to bypass the Windows resolver). > | That information is not present currently [ and nobody asks for it :) ] > | I wonder if we should add it and where to place it. One option is the > | User's Guide. Another option is a custom resolv.conf man page. > | What do you think? > | > | Pierre
----- End forwarded message -----
