hmmm, maybe another way to do this. check jobs for a wget pid. If found
wget is running and not found wget either hasn't started or has stopped.
--
Jude <jdashiel at panix dot com>
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo.
Please use in that order."
Ed Howdershelt 1940.
On Sun, 17 Mar 2024, Didier Spaier wrote:
Hi,==============================================================================The
As far as I know wget only returns an error code when it terminates.
"man wget" lists these error codes under the title "exit status", quoted
below:
Wget may return one of several error codes if it encounters problems.
0 No problems occurred.
1 Generic error code.
2 Parse error---for instance, when parsing command-line options, the
.wgetrc or .netrc...
3 File I/O error.
4 Network failure.
5 SSL verification failure.
6 Username/password authentication failure.
7 Protocol errors.
8 Server issued an error response.
With the exceptions of 0 and 1, the lower-numbered exit codes take
precedence over higher-numbered ones, when multiple types of errors are
encountered.
Cheers,
Didier
Le 17/03/2024 à 15:58, Jude DaShiell a écrit :
Does anyone know what error level wget returns while wget is in process of===============================================================================
a download?
The Slint mailing list.
Archive: https://www.freelists.org/archive/slint
To subscribe or unsubscribe, email slint-request@xxxxxxxxxxxxx with the
subject
'subscribe' or 'unsubscribe', then answer the email you will receive.
More: email slint-request@xxxxxxxxxxxxx with as subject 'help' or 'commands'.
