(I'll trim messages in the future.)
BTW - a message I posted after this one yesterday bounced. Basically, it
said that I didn't notice until after my initial post that I had been
using 4.0.3 before, and now have 4.1 (as of yesterday). Same problem
happened with both.
The system clock on my computer is correct. The system clock on the host
from where I ftp the file is about 10 minutes ahead of mine. (I get the
same problem if I run Analog against the ftp'd file later on, too, not
just immediately thereafter.) Interesting question, though - I just
replaced the battery in my computer, I don't know whether it coincided
with that - it was around the same time as the month roll for the
DNSGOODHOURS. (When the battery went and it defaulted, it went to a
date/time in something like 1958, not in the future.)
Maybe I'll try waiting to run Analog for 10+ minutes after I ftp the
file...
Otherwise:
-DNS is set to WRITE.
-No dnslock files are in the same folder - and I even went looking with a
utility for hidden ones.
-There is only one occurrence each of DNS, DNSGOODHOURS and DNSBADHOURS
in the config file.
-Analog failed when I renamed analog.cfg.
Cathleen
On 4/24/00 1:41 PM, Jason Linhart wrote:
>On 4/23/00 4:32 PM camccli ([EMAIL PROTECTED]) wrote:
>
>>I've looked in the documentation and the FAQ and the archive, and I can't
>>seem to find the answer to this.
>>
>>I'm running Analog 4.1 on a PowerMac 7300, System 8.1. I downloaded it
>>about a month ago, and everything was fine up until a couple of days ago.
>>Now, *every* time I run Analog, it looks up *every* IP address. I've
>>deleted the dnscache, run Analog to create a new dnscache, then
>>immediately rerun it - and it looks everything up again. (I do have it in
>>WRITE mode.)
>>
>>I had initally left the DNSGOODHOURS at the default setting of 672 (four
>>weeks). It seems that this started happening at the four-week mark. I've
>>since changed the DNSGOODHOURS to other values, but it hasn't made a
>>difference. I also re-downloaded Analog today in case in my playing with
>>the config file, I messed something up, but... still the same problem.
>
>The most likely thing is that your system clock is set far into the
>future. There are other possibilities, make sure DNS is set to WRITE and
>not LOOKUP, make sure there isn't a dnslock file in the same folder as
>the Analog application, check for multipule definitions of DNS,
>DNSGOODHOURS, and DNSBADHOURS in the analog.cfg file, make sure you are
>using the analog.cfg file you thing you are using (rename the file and
>run Analog, if Analog doesn't fail you have the wrong analog.cfg file).
>
>Jason
>
>
>-----------------
>[EMAIL PROTECTED]
>-----------------
>Dr. Seuss books . . . can be read and enjoyed on several levels. For
>example, 'One Fish Two Fish, Red Fish Blue Fish' can be deconstructed
>as a searing indictment of the narrow-minded binary counting system.
> -- Peter van der Linden, Expert C Programming, Deep C Secrets
------------------------------------------------------------------------
This is the analog-help mailing list. To unsubscribe from this
mailing list, send mail to [EMAIL PROTECTED]
with "unsubscribe" in the main BODY OF THE MESSAGE.
List archived at http://www.mail-archive.com/[email protected]/
------------------------------------------------------------------------
