At 09:45 AM 11/4/99 +0000, Stephen Turner wrote:
> On Thu, 4 Nov 1999, Jason Linhart wrote:
> 
> > On 11/3/99 9:23 PM Mitch Kutzko ([EMAIL PROTECTED]) wrote:
> > 
> > >Can someone please try to tell me what's wrong with the FILEEXCLUDE I'm
> > >trying to get to work?  As I said in my previous posting, an "analog
> > >-settings" *says* things are set right, but the Images directory is still
> > >included in the stats.
> > 
> > Could you tell us all of the FILEINCLUDE and FILEEXCLUDE commands you 
> > have, in the order they appear in your configuration file. And can you 
> > also give us the exact text of one of the requests that you think should 
> > be excluded?

Here are the main guts from analog.cfg.  I've made almost no changes to the
template file supplied in the distribution.

PAGEINCLUDE *.ps,*.ps.gz
REQINCLUDE pages
LOGO "/Images/dast.gif"
LOGFORMAT MICROSOFT-NA
LOGFILE "C:\winnt\system32\logfiles\*.log"
IMAGEDIR "/stats/WebAnalogImages/"
HOSTNAME "NLANR/DAST, Year 2"
HOSTURL "http://dast.nlanr.net/"
OUTFILE "D:\inetpub\htdocs\stats\year2_noimages_noncsa.html"
ALL ON
FROM 981001
TO 990930
FILEEXCLUDE /Images/*
LINKINCLUDE pages
HOSTEXCLUDE 141.142.*.*
HOSTEXCLUDE 192.17.21.181
HOSTEXCLUDE 204.123.9.52
HOSTEXCLUDE 208.219.77.19

The only thing in the file below this are the multiple BROWOUTPUTALIAS,
REFALIAS, and TYPEOUTPUTALIAS statements that came with the distribution
sample file.

I'd expect that all of these image references would be excluded:

GET, /Images/consult2.gif, -, 
209.197.209.192, -, 8/27/99, 0:32:27, W3SVC, DAST, 141.142.5.17, 2359, 259,
260, 200, 0, GET, /Images/white.gif, -, 
138.26.15.176, -, 8/27/99, 0:34:34, W3SVC, DAST, 141.142.5.17, 0, 264, 72,
304, 0, GET, /index.html, -, 
138.26.15.176, -, 8/27/99, 0:34:35, W3SVC, DAST, 141.142.5.17, 1344, 311,
72, 304, 0, GET, /Images/white.gif, -, 
138.26.15.176, -, 8/27/99, 0:34:35, W3SVC, DAST, 141.142.5.17, 156, 312,
72, 304, 0, GET, /Images/dast.gif, -, 
138.26.15.176, -, 8/27/99, 0:34:35, W3SVC, DAST, 141.142.5.17, 219, 319,
72, 304, 0, GET, /Images/Blackholes.gif, -, 
138.26.15.176, -, 8/27/99, 0:34:35, W3SVC, DAST, 141.142.5.17, 0, 315, 72,
304, 0, GET, /Images/getstart.gif, -, 
138.26.15.176, -, 8/27/99, 0:34:35, W3SVC, DAST, 141.142.5.17, 0, 311, 72,
304, 0, GET, /Images/help.gif, -, 
138.26.15.176, -, 8/27/99, 0:34:35, W3SVC, DAST, 141.142.5.17, 0, 315, 72,
304, 0, GET, /Images/resource.gif, -, 
138.26.15.176, -, 8/27/99, 0:34:36, W3SVC, DAST, 141.142.5.17, 328, 319,
72, 304, 0, GET, /Images/nsf_t_logo.gif, -, 
138.26.15.176, -, 8/27/99, 0:34:36, W3SVC, DAST, 141.142.5.17, 282, 314,
72, 304, 0, GET, /Images/relate.gif, -, 

> And any FILEALIASes.

No FILEALIAS commands at all.

> You could include a pointer to the URL of the report too if you want.

http://dast.nlanr.net/stats/year2_noimages_noncsa.html
> 
> > The first INCLUDE/EXCLUDE that matches is the one used. Also it is easy 
> > to mis-spell things when making up INCLUDE/EXCLUDE statments.
> > 
> Your command certainly looked right. I wonder if case sensitivity could be a
> problem. If you're running analog on a Unix machine, and you exclude
> /Images/* it won't also exclude /images/* . So if your logs come from a
> Windows machine but you're running the analysis on a Unix machine, you need
> to set CASE INSENSITIVE.

Our web server is run, the stats are stored, and analog is run on the same
Windows box, which is running NT Server 4.0, SP3.  Haven't tried CASE
INSENSITIVE, but will if you think it'll make any difference.  (I don't
think it will, though... ;-) ) 


Thanks for looking at this!

Mitch
--
Mitch Kutzko | [EMAIL PROTECTED] | [EMAIL PROTECTED] | 217-333-1199
http://hobbes.ncsa.uiuc.edu/
--
A Polar bear is really just a Cartesian bear undergoing a coordinate
transformation.
------------------------------------------------------------------------
This is the analog-help mailing list. To unsubscribe from this
mailing list, send mail to [EMAIL PROTECTED]
with "unsubscribe analog-help" in the main BODY OF THE MESSAGE.
List archived at http://www.mail-archive.com/[email protected]/
------------------------------------------------------------------------

Reply via email to