From: "Webmaster" <[EMAIL PROTECTED]>
> I set analog to do a dns lookup as follows:
>
> DNSFILE C:\rlws\www\analog\dnscache.txt
> DNS WRITE
> DNSBADHOURS 48
>
> when I executed analog.exe the command line window opened with a
> flashing curser.
Analog is a console mode program - it's supposed to run in a command line
window.
> it's been sitting like that for about 4 hours. I realize that this
> look up could take awhile but should it be that long?
That rather depends on how big your log file is, and how fast your DNS
server is. DNS lookups are done one at a time, and are far, far slower
than anything else that Analog does. If you're analysing a large log file,
and your DNS server is slow (or has a slow connection to upstream DNS
servers), Analog can take a very long time indeed to do DNS lookups.
That's why there's a whole section on the Helper applications page for DNS
lookup tools: http://analog.sourceforge.net/helpers/index.html#dns
And it's unlikely that unresolved IP addresses will start resolving in 2
days time, so I'd be inclined to up your DNSBADHOURS figure.
Aengus
+------------------------------------------------------------------------
| This is the analog-help mailing list. To unsubscribe from this
| mailing list, go to
| http://lists.isite.net/listgate/analog-help/unsubscribe.html
|
| List archives are available at
| http://www.mail-archive.com/[email protected]/
| http://lists.isite.net/listgate/analog-help/archives/
| http://www.tallylist.com/archives/index.cfm/mlist.7
+------------------------------------------------------------------------
