> WHY IS -t 2, -T 900 and the --cache=off options being ignored when I run
> this in a cron job?
If you're troubled by the message "Caching oiswww.eumetsat.int =>
81.2.148.34", then the explanation may be that "--cache=off" differs
from "--dns-cache=off". As "wget -h" says:
--no-cache disallow server-cached data.
--no-dns-cache disable caching DNS lookups.
(The reason every option comes in two different forms may belong in a
different complaint.)
The "-t 2" seemed to me to work as expected. (On my system, I see a
"Setting --tries (tries) to 2" message _before_ the "DEBUG output
created by [...]", but you do seem to get two tries followed by "Giving
up." when the second one fails. What were you expecting?
As for "-T 900", with no times in your debug output, how can anyone
say if it's working as expected? (Again, on my system, I see a "Setting
--timeout (timeout) to 900" before the "DEBUG output created by [...]".)
I don't know why a given script fails in a "cron" job when it works
interactively on your (unknown) version of GNU/Linux. I can imagine
that a low priority "cron" job gets no CPU time on a busy system, but
knowing practically nothing about your environment, my speculation is
probably not worth much. You might throw some "date" or "time" commands
into it to see how much time is being spent doing what. Do you know
that the "wget" being run is the same in both cases? A simpler test
script which could all be revealed (instead of "Part of my script
[...]") might also be helpful. You might also try a "cron" job with
some other task to see if it completes in a reasonable amount of time.
------------------------------------------------------------------------
Steven M. Schweda (+1) 651-699-9818
382 South Warwick Street [EMAIL PROTECTED]
Saint Paul MN 55105-2547
