/Hi,
/
/> echo nameserver 8.8.8.8 > /etc/resolv.conf /
/> /
/> The file is getting updated and the operation exits with error
"Timeout was /
/> reached". /
Sorry, but is that the error message from curl when it fails?
/Yes that is the error message from curl when it fails. /
/> I am able to "ping www.google.com" and "ping my_ftp_server" with
8.8.8.8 as /
/> the only entry in the resolv.conf file, but the curl operation fails. /
Which libcurl version? On Linux? What name resolver backend does your
libcurl
use? 'curl -V' shows.
/Sorry, I missed out the libcurl version in my querry. It is 7.45. I am
using debian jessie in Beaglebone Black.
I have cross compiled curl and is using the library from my application.
I have compiled the library with "--enable-threaded_resolver". curl -V
gives the following output:/
curl 7.48.0 (armv7l-unknown-linux-gnueabihf) libcurl/7.38.0
OpenSSL/1.0.1k zlib/1.2.8 libidn/1.29 libssh2/1.4.3 librtmp/2.3
Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps
pop3 pop3s rtmp rtsp scp sftp smtp smtps telnet tftp
Features: AsynchDNS IDN IPv6 Largefile GSS-API SPNEGO NTLM NTLM_WB SSL
libz TLS-SRP
Can you please be more specific about the exact error message and return
code
you get from libcurl?
/The error code is 28 and the error message is /Timeout was //reached//
As Dan Fandrich already asked you on curl-users: Can you use the Google DNS
server manually? e.g. does "host www.google.com 8.8.8.8" or "dig
www.google.com @8.8.8.8" return anything?
The following is the output for host www.google.com 8.8.8.8
/root@arm:/home/debian# echo nameserver 8.8.8.8 > /etc/resolv.conf
root@arm:/home/debian# cat /etc/resolv.conf
nameserver 8.8.8.8
root@arm:/home/debian# host //www.google.com//8.8.8.8
Using domain server:
Name: 8.8.8.8
Address: 8.8.8.8#53
Aliases:
//www.google.com//has address 216.58.197.68 //
www.google.com//has IPv6 address 2404:6800:4007:806::2004/
_//_
Regards
Ison Thomas
On Tuesday 03 May 2016 03:30 PM, [email protected] wrote:
Send curl-library mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
http://cool.haxx.se/cgi-bin/mailman/listinfo/curl-library
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of curl-library digest..."
Today's Topics:
1. now checking more docs with tests (Daniel Stenberg)
2. Re: now checking more docs with tests (Dan Fandrich)
3. FTP operation timeout when public DNS Server is used (Ison)
----------------------------------------------------------------------
Message: 1
Date: Tue, 3 May 2016 00:01:11 +0200 (CEST)
From: Daniel Stenberg <[email protected]>
To: libcurl hacking <[email protected]>
Subject: now checking more docs with tests
Message-ID: <[email protected]>
Content-Type: text/plain; format=flowed; charset=US-ASCII
Hey just a FYI here,
Just wanted to mention that I added test 1139 and 1140 the last couple of
days. They do all sorts of fun verifications of docs:
test 1139 runs manpage-scan.pl which
1. checks that all CURLOPT_ options mentioned in symbols-in-versions have
their own man pages _and_ are mentioned in curl_easy_setopt.3
2. checks that all CURLINFO_ options mentioned in symbols-in-versions have
their own man pages _and_ are mentioned in curl_easy_getinfo.3
3. checks that all CURLMOPT_ options mentioned in symbols-in-versions have
their own man pages _and_ are mentioned in curl_multi_setopt.3
4. checks that the code that shows curl -h, the code that lists all command
line options for the parser and curl.1 all mention the same set of command
line options. Any and all mismatches are reported. There's a whitelisting
concept to allow curl -h to not include deprecated options.
test 1140 runs nroff-scan.pl which goes through all nroff formatted man pages
we have (about 346 files right now) and:
1. checks that all references to curl symbols are all within \fI and \fP
2. checks that the targets in references are actual existing man pages
3. checks for mentions of curl symbols with (3) added, that isn't written to
become a reference
While writing these scripts I of course detected a busload of mistakes in the
docs that I've pushed. My hope is that these scripts will help us reduce the
number of documentation mistakes we commit and help us detect them when we
forget. As the tests also run on pull-requests, they will help contributors to
get their patches with docs done correctly.
Let me know if you get or see any problems because of these!
-------------------------------------------------------------------
List admin: https://cool.haxx.se/list/listinfo/curl-library
Etiquette: https://curl.haxx.se/mail/etiquette.html
