This chapter contains all the stuff that could not fit anywhere else.
Like all GNU utilities, the latest version of Wget can be found at the master GNU archive site prep.ai.mit.edu, and its mirrors. For example, Wget 1.5.1 is at:
I'll try to make a "real" home page for Wget some time in the future. If you would like to do it, please say so--I'll be delighted.
Wget has its own mailing list at
to Karsten Thygesen. The mailing list is for discussion of Wget
features and web, reporting Wget bugs (those that you think may be of
interest to the public) and mailing announcements. You are welcome to
subscribe. The more people on the list, the better!
To subscribe, send mail to
the magic word `subscribe' in the subject line. Unsubscribe by
The mailing list is archived at
You are welcome to send bug reports about GNU Wget to
<email@example.com>. The bugs that you think are of the
interest to the public (i.e. more people should be informed about them)
can be Cc-ed to the mailing list at
Before actually submitting a bug report, please try to follow a few simple guidelines.
gdb `which wget` coreand type
whereto get the backtrace.
Since Wget uses GNU Autoconf for building and configuring, and avoids using "special" features of any one Unix system, it should compile (and work) on all common flavors of Unix.
This version was compiled and tested this version on various Unix systems, including Solaris, Linux, SunOS, OSF (aka Digital Unix), and Ultrix; refer to the file `MACHINES' in the distribution directory for a comprehensive list. If you compile it on an architecture not listed there, please let me know.
Wget should also compile on the other Unix systems, not listed in `MACHINES'. If it doesn't, please let me know.
Thanks to Darko Budor and other contributors, this version of Wget
compiles and works on Windows 95 and Windows NT platforms. It has been
compiled successfully using MS Visual C++ 4.0 and Watcom C compiler,
with Winsock as networking software. Of course, it is crippled of many
features available on Unix, but it should work as a substitute for
people stuck with Windows. Note that the Windows port is
neither tested nor maintained by me, or anyone at GNU--all
questions and problems should be reported to
Since the purpose of Wget is background work, it catches the hangup
SIGHUP) and ignores it. If the output was on standard
output, it will be redirected to a file named `wget-log'.
SIGHUP is ignored. This is convenient when you wish
to redirect the output of Wget after having started it.
$ wget http://www.ifi.uio.no/~larsi/gnus.tar.gz & $ kill -HUP %% # Redirect the output to wget-log
Other than that, Wget will not try to interfere with signals in any
kill -TERM and
kill -KILL should kill it
Go to the first, previous, next, last section, table of contents.