Both 1 and 2 can be arranged by your script, surely? I wrote a similar script myself recently (albeit in Access) for my organisation.
*********** REPLY SEPARATOR *********** On 23/06/2004 at 15:04 [EMAIL PROTECTED] wrote: >I sent the following immediately on joining this list and having received >no resopnse I >wondered if it was not actually published. If it was, my apologies for the >repeat posting >but I would appreciate any comments and help. Thank you. > >I've been using Analog for several years, compiling stats locally "by >hand". I'm now >trying to set up an automated service for my customers on a Windows 2000 >server >using ASP under IIS5. The server has several virtual web sites, each web >site having >an unique log path within the site's directory structure. > >Most of the problems are solved. I have created generic cfg scripts as far >as possible >and each site's "personal" script is down to the name and address of the >files plus a >little bit of site-specific setup. Analog is called direct from ASP with >the name of the >site-specific script and the From - To range of dates. > >Unfortunately the site's personal script can only specify a full Logfile >path and name. I >know about the wildcards and date variables in the name but they are not >suitable in >this case. > >What I need to specify in the script is the LogPath - where the logs can >be found - not >the full LogFile details. I can't easily use the full path names in the >command line >because the log directory is a variable under IIS and has an unique number >specified >by to the site's ID. There is a way of specifying this directory name >within my coding >but it's messy. > >With a LOGPATH the LOGFILE on the command line would only need to specify >the >log filenames which, being predictable (year-month-day), can be >pre-calculated. The >alternative is a very long command line string with the full path to the >logs for, say, the >past 26 weeks - potentially 180 names but with a bit of work maybe a >dozen, by >creating monthly wildcards plus the odd ones. Although tedious, this can >be done (but >see below). > >The apparent solution of using the FROM and TO commands is not a good one. >The >dates may be used to refine the criteria within a specified range of log >files but the >method of reading every line in every log file to find suitable dates >(which seems to be >what's happening, judging by working time) is unacceptable where the total >size of the >logs may be several hundred megabytes across several hundred files. The >whole point >of my code is in avoiding excessive log processing times. > >I have read quite a few Help forum messages over the past few hours, >trying to find a >work-around, and I notice several other people with similar problems, >though not >always in a Windows environment. > >Pulling the above together, what I propose is: > >1. A new command LOGPATH to specify ONLY the path. If this command is >specified >anywhere then any and all LOGFILE commands would be appended to it as >appropriate - they could still include final path segments but probably >wouldn't. >LOGPATH could be a command line argument as well as a scripted one. > >2. A mechanism similar to FROM and TO that would specify a range of >LOGFILE >substitutions, similar to the month/year variables but giving a range of >"names" - eg: > >LOGFILE ex%from.log >LOGFILE ex%to.log > >... where %from might be specified on the command line as +LF040514 and >%to as >+LT040614 (or whatever switch characters are suitable). Multiple instances >of these >commands might be useful (specify files for first week of every month) but >probably >unnecessary. > >___________ >Dave Stiles >+------------------------------------------------------------------------ >| TO UNSUBSCRIBE from this list: >| http://lists.isite.net/listgate/analog-help/unsubscribe.html >| >| Digest version: http://lists.isite.net/listgate/analog-help-digest/ >| Usenet version: news://news.gmane.org/gmane.comp.web.analog.general >| List archives: http://www.analog.cx/docs/mailing.html#listarchives >+------------------------------------------------------------------------ +------------------------------------------------------------------------ | TO UNSUBSCRIBE from this list: | http://lists.isite.net/listgate/analog-help/unsubscribe.html | | Digest version: http://lists.isite.net/listgate/analog-help-digest/ | Usenet version: news://news.gmane.org/gmane.comp.web.analog.general | List archives: http://www.analog.cx/docs/mailing.html#listarchives +------------------------------------------------------------------------
