Hi,
I would like to exclude different browsers from my reporting.
I Included the following HTML in the basic form
BRINPUT TYPE=radio NAME=bz VALUE="Slurp" checked
[On] INPUT TYPE=radio NAME=cq [Off] Exclude Slurp
BRINPUT TYPE=radio NAME=bz VALUE="ArchitextSpider"
checked [On] INPUT
I'm trying to do some massaging of host/dmomain names as part of an
anlog run, rather than do it using grep/awk/sed etc.
I'm running against intranet domain names which are of the form
host.section.department.
eg it1.it.finance, where the IT section is part of Finance Department.
Some of the old
LOGFIX.VBS is a VBScript script/program, so you have to have Windows
Scripting Host installed. (It's installed by default when you install
IIS4, as far as I can remember, so a .VBS script may be a better option
than a perl script for people who aren't comfortable with installing
perl on their
On Mon, 20 Sep 1999, Stephen Turner wrote:
ST When I specify a log file on the command line 'analog /var/log/wn.log.001'
ST it aborts and tells me that there are too many corrupted lines in the file.
ST When I put the same logfile in analog.cfg, it does it just fine.
ST
STMaybe there's a
On 9/21/99 11:56 AM Jim Balcom ([EMAIL PROTECTED]) wrote:
On Mon, 20 Sep 1999, Stephen Turner wrote:
ST When I specify a log file on the command line 'analog
/var/log/wn.log.001'
ST it aborts and tells me that there are too many corrupted lines in
the file.
ST When I put the same logfile in
I need help with compiling via gcc on a Solaris machine. Everytime i try
to "make" analog, it fails. I have tried re-downloading 3 times, and
re-taring 3-4 times of each. But everytime I get to the make stage I get
a new error. Is there a known problem with the solaris (5.5.1) compiling
of
On 9/21/99 9:09 PM [EMAIL PROTECTED] ([EMAIL PROTECTED]) wrote:
I need help with compiling via gcc on a Solaris machine. Everytime i try
to "make" analog, it fails. I have tried re-downloading 3 times, and
re-taring 3-4 times of each. But everytime I get to the make stage I get
a new error.
Maybe there's a LOGFORMAT command in analog.cfg which is telling analog the
log format when the LOGFILE command is in analog.cfg too, but analog doesn't
know the format when the logfile is specified on the command line.
Perhaps I should be more explicit. All commands work on the command
