$K_SEVERE 4 /* SEVERE ERROR
*/
Note that success (including informational) is odd, while anything worse
is even.
While an OS like UNIX is handicapped by not having such a useful
convention, it would make sense for Wget to have status values which
values.)
mmh, i don't understand why we should use VMS-specific values in wget.
On VMS (not elsewhere), Wget should use VMS-specific values. The VMS
C RTL is willing to convert 0 into a generic success code, but 1 (EPERM,
Not owner) and 2 (ENOENT, No such file or directory) would tend
Alle 18:06, lunedì 19 settembre 2005, Hrvoje Niksic ha scritto:
Mauro Tortonesi [EMAIL PROTECTED] writes:
mmh, i don't understand why we should use VMS-specific values in
wget.
The closest Unix has to offer are these BSD-specific values which few
programs use:
/*
* SYSEXITS.H -- Exit
Mauro Tortonesi [EMAIL PROTECTED] writes:
yes, but i was thinking to define wget specific error codes.
I wouldn't object to those. The scripting people might find them
useful.
I'm not sure if this is a bug or a feature, but with recursive
operation, if a get fails and retrieve_tree bails out then no sensible
error codes are returned to main.c (errors are only passed up if the
user's quota was full, the URL was invalid or there was a write error)
so retrieve_tree always
Owen Cliffe [EMAIL PROTECTED] writes:
Is there a good reason why retrieve tree doesn't just return the
status of the last failed operation on failure?
The original reason (which I don't claim to be good) is because Wget
doesn't stop upon on error, it continues. Because of this returning a
Alle 18:58, mercoledì 14 settembre 2005, Hrvoje Niksic ha scritto:
Owen Cliffe [EMAIL PROTECTED] writes:
Is there a good reason why retrieve tree doesn't just return the
status of the last failed operation on failure?
The original reason (which I don't claim to be good) is because Wget
I downloaded the official wget 1.9 sources and, following some
suggestions that were given to me, temporarily renamed a bunch of SSL
libraries that were already on my system that seemed to be confusing
the linker... And it all works!
Compiled wget 1.9 successfully under Mac OS X 10.2.8 on a
certificate it can retrieve the page too).
Therefor I wouldn't expect a Read error (Success) in retreiving
https://145.222.136.165 maybe a warning about verification, but
it should continue, like it does for the woz-online.amsterdam.nl URL.
BTW, the dns has been updated, so https
Hi,
I'm having trouble connecting with wget to a site using SSL:
wget https://145.222.135.165/index.htm
--13:46:36-- https://145.222.135.165/index.htm
= `index.htm'
Connecting to 145.222.135.165:443... connected.
HTTP request sent, awaiting response...
Read error (Success) in headers
://145.222.135.165/index.htm
= `index.htm'
Connecting to 145.222.135.165:443... connected.
HTTP request sent, awaiting response...
Read error (Success) in headers.
Retrying.
--13:46:37-- https://145.222.135.165/index.htm
(try: 2) = `index.htm'
Connecting to 145.222.135.165:443... connected
On Fri, 19 Sep 2003, Hrvoje Niksic wrote:
wget https://145.222.135.165/index.htm
--13:46:36-- https://145.222.135.165/index.htm
= `index.htm'
Connecting to 145.222.135.165:443... connected.
HTTP request sent, awaiting response...
Read error (Success) in headers.
Retrying
Hello all,
I am new to this as I have just downloaded wget and an aqua shell for
OSX in order to try to download the posts that reside in my online
community at www.communityzero.com/imperium.
The problem I seem to be having is that any request to download
recursively, or even just one
Executive summary: complete success.
On NCR MP-RAS, Wget 1.7.1-pre1 configured and compiled fine, and
passed a few simple tests. The -lnsl/-lsocket and MAP_FAILED
problems seen with previous versions did not occur.
No SSL library is installed on the system. ./configure
--with-ssl detected
Andre Majorel [EMAIL PROTECTED] writes:
Executive summary: complete success.
[...]
Thanks a lot for testing.
15 matches
Mail list logo
