Bonno Bloksma wrote:
Hi Pete,
In your first mail about this problem you wrote:
/There has long been a bug in the getRulebase script using wget which
causes the rulebase file that is downloaded to have the local system's
timestamp. Under normal circumstances this does not cause a problem
becaus
Stefan Paege wrote:
Pete,
to make your long (and interesting) story short:
There is no need to use the "updated improved Script"!
We can continue to use the "old" WGet/NonCURL script!
Correct?
Almost, but not quite.
The new script is still better and should be used instead of the old
sc
Hi Pete,
In your first mail about this problem you wrote:
There has long been a bug in the getRulebase script using wget which
causes the rulebase file that is downloaded to have the local system's
timestamp. Under normal circumstances this does not cause a problem
because most system clocks ar
Pete,
to make your long (and interesting) story short:
There is no need to use the "updated improved Script"!
We can continue to use the "old" WGet/NonCURL script!
Correct?
--
elektronik-labor CARLS GmbH & Co. KG
Stefan Paege
Fon: +49 5973 9497-23
Fax: +49 5973 9497-19
elektronik-
Bonno Bloksma wrote:
Hi Pete,
I get what you said. But:
/ I'm nowhere near your timezone, I'm at GMT+1 or +2. So should there
not have been a problem long before where my system would see older
files at your system several times a day when in fact there would be a
newer one?/
/*Does that mea
Hi Pete,
I get what you said. But:
I'm nowhere near your timezone, I'm at GMT+1 or +2. So should there not have
been a problem long before where my system would see older files at your system
several times a day when in fact there would be a newer one?
Does that mean my system has been getting