On Sun, 09 Dec 2007 13:19:51 -0800
Micah Cowan wrote:
I believe I already answered this: it is because a non-zero exit
status always means something's wrong. Myriad scripts invoke
utilities in ways similar to:
if ! wget http://foo.com/
then
echo Something went wrong with the download.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
R Kimber wrote:
On Sun, 09 Dec 2007 13:19:51 -0800
Micah Cowan wrote:
I believe I already answered this: it is because a non-zero exit
status always means something's wrong. Myriad scripts invoke
utilities in ways similar to:
if ! wget
On December 09, 2007 at 07:03PM Stuart Moore wrote:
Could the exit code used be determined by a flag? E.g. by default it
uses unix convention, 0 for any success; with an
--extended_error_codes flag or similar then it uses extra error codes
depending on the type of success (but for sanity
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gerard wrote:
On December 09, 2007 at 07:03PM Stuart Moore wrote:
Could the exit code used be determined by a flag? E.g. by default it
uses unix convention, 0 for any success; with an
--extended_error_codes flag or similar then it uses extra
On Saturday December 08, 2007 at 09:18:08 (PM) Micah Cowan wrote:
So, perhaps its time to come back to the question of differentiated exit
codes from Wget. This may be a 1.12 question, or perhaps a 1.13
question, but at any rate, with 1.11 ready to go out the day, we perhaps
have a little
Gerard [EMAIL PROTECTED] writes:
In particular, if Wget chooses not to download a file because the
local timestamp is still current, or because its size corresponds
to that of the remote file, these should result in an exit status
of zero.
I disagree. If wget has not downloaded a file,
On Sun, 09 Dec 2007 21:13:32 +0100
Hrvoje Niksic wrote:
I disagree again. If wget did not download a file, no matter what
the reason, then it should not exit with zero. I have written
several scripts that utilize wget to download files. Because wget
fails to issue a useful code upon
On Sunday December 09, 2007 at 03:13:32 (PM) Hrvoje Niksic wrote:
Gerard [EMAIL PROTECTED] writes:
In particular, if Wget chooses not to download a file because the
local timestamp is still current, or because its size corresponds
to that of the remote file, these should result in an
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
R Kimber wrote:
On Sun, 09 Dec 2007 21:13:32 +0100
Hrvoje Niksic wrote:
I disagree again. If wget did not download a file, no matter what
the reason, then it should not exit with zero. I have written
several scripts that utilize wget to
R Kimber [EMAIL PROTECTED] writes:
I agree that Wget should allow the caller to find out what
happened, but I don't think exit codes can be of much use there.
For one, they don't allow distinction between different
successful conditions, which is a problem in many cases.
I'm not sure I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gerard wrote:
On Sunday December 09, 2007 at 03:13:32 (PM) Hrvoje Niksic wrote:
Gerard [EMAIL PROTECTED] writes:
In particular, if Wget chooses not to download a file because the
local timestamp is still current, or because its size corresponds
On December 09, 2007 at 04:19PM Micah Cowan wrote:
I believe I already answered this: it is because a non-zero exit status
always means something's wrong. Myriad scripts invoke utilities in
ways similar to:
if ! wget http://foo.com/
then
echo Something went wrong with the download.
fi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gerard wrote:
On December 09, 2007 at 04:19PM Micah Cowan wrote:
I believe I already answered this: it is because a non-zero exit status
always means something's wrong. Myriad scripts invoke utilities in
ways similar to:
if ! wget
On 09/12/2007, Micah Cowan [EMAIL PROTECTED] wrote:
Non-zero exit statuses indicate failure, partial or complete. I am not
going to try to use them to mean something else. Exit codes are, plain
and simple, the wrong way to communicate these differences. Perhaps if,
in the early days, the
On Dec 9, 2007 7:03 PM, Stuart Moore [EMAIL PROTECTED] wrote:
Could the exit code used be determined by a flag? E.g. by default it
uses unix convention, 0 for any success; with an
--extended_error_codes flag or similar then it uses extra error codes
depending on the type of success (but for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
So, perhaps its time to come back to the question of differentiated exit
codes from Wget. This may be a 1.12 question, or perhaps a 1.13
question, but at any rate, with 1.11 ready to go out the day, we perhaps
have a little more time to discuss it in
Hi,
does anybody if there is a complete and correct docu of all
wget exit codes, so I could use them in a shell programm for
logging purposes for example.
Regards
Georg E. Paulusberger
SysAdmin, Salzburg
17 matches
Mail list logo
