LQ Suggestions & FeedbackDo you have a suggestion for this site or an idea that will make the site better? This forum is for you.
PLEASE READ THIS FORUM - Information and status updates will also be posted here.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hi. I have a problem--seemingly elinks won't talk nicely to the LQ search facilities.
When a search query succeeds (I define this as me not recieving the message "you can only search every 40 seconds, please wait another n seconds"), all I see is an empty page. When I view source, it's still an empty page.
So far, I've tried versions 0.10.6-1 and 0.10.4-7, both debian builds (and the result is the same). I've included the information that the debian-bug emacs function outputs for elinks, the elinks --version output and a link to my ~/.elinks/elinks.conf file.
Lynx and w3m all seem to handle LQ just fine, so I think this is a links problem. If you can reproduce this, I'd like to know. If you can't, I'd like to know what you're doing differently from me. Of course, if you know why this happens and/or how I can fix this, I'd very much like to know.
Code:
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.8-1-686
Locale: LANG=C, LC_CTYPE=C (charmap=ISO-8859-1) (ignored: LC_ALL set to en_GB.ISO-8859-1)
Versions of packages elinks depends on:
ii debconf 1.4.70 Debian configuration management sy
ii libbz2-1.0 1.0.3-2 high-quality block-sorting file co
ii libc6 2.3.5-6 GNU C Library: Shared libraries an
ii libexpat1 1.95.8-3 XML parsing C library - runtime li
ii libgnutls11 1.0.16-14 GNU TLS library - runtime library
ii libgpmg1 1.19.6-21 General Purpose Mouse - shared lib
ii libidn11 0.5.18-1 GNU libidn library, implementation
ii liblua50 5.0.2-5.1 Main interpreter library for the L
ii liblualib50 5.0.2-5.1 Extension library for the Lua 5.0
ii libperl5.8 5.8.7-10 Shared Perl library
ii zlib1g 1:1.2.3-9 compression library - runtime
elinks recommends no packages.
-- no debconf information
elinks --version
Code:
ELinks 0.10.6 (built on Sep 17 2005 18:12:19)
Features:
Standard, Fastmem, IPv6, gzip, bzip2, Cascading Style Sheets, Protocol (File, FTP, HTTP, NNTP, SMB, URI rewrite, User protocols),
SSL (GnuTLS), MIME (Option system, Mailcap, Mimetypes files), LED indicators,
Bookmarks, Cookies, Form History, Global History, Scripting (Lua, Perl)
Of course, I searched both google and LQ, and all pages/threads looked unrelated (and the ones I looked at were unrelated, so I extrapolated from those).
You mean bugs.linuxquestions.org? "unable to retrieve <the url>: host not found". No other LQ/google searches come up with anything relevant. Possibly an ISP or PEBKAC error--not sure. I haven't used the bug tracker before, so I don't know, but could someone else enter the info, or would that lose some specific-to-me-'ness? Anyways, I'll try again later, but I'm also open to duct tape/WD-40 work-arounds
jonaskoelker, I think the config problem is at your end. LQ searches can take a little bit of time due to the limited hardware available at the moment and you are timing out at 2 minutes and then retrying:
Code:
## connection.receive_timeout <num>
# Receive timeout (in seconds).
set connection.receive_timeout = 120
## connection.retries <num>
# Number of tries to establish a connection.
# Zero means try forever.
set connection.retries = 3
I'd try setting connection.receive_timeout to 600 (a bit over the top but good for testing) and see if that fixes it. You are likely to get the 40 second warning because of the second retries option. I'm not sure why if it really is trying every 120 seconds but my guess is that it may be trying sooner or piplining multiple requests.
david_ross: That didn't work--I tried setting it to 1800 (the largest value) as well.
Harishankar: most likely. Try fiddling around with the configuration. Compare it with mine also, and post a link to your file if all else fails. Btw, is it links or elinks (there is a difference)?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.