From: "Chuck Schick" <[EMAIL PROTECTED]> > We do commercial web hosting and I want to Automate running analog so that > it will run for each domain and put the output in unique folders for each > domain. I understand that this can be readily be done by setting up a > config file for each domain. My initial experiment will be on a Windows NT > server. My present idea is to run analog on a weekly log file and then > place the output in a subdirectory for the domain. My questions are this: > > 1) Most domains are set up with log files running weekly. When a week ends > is there an automated way to copy the log file to a different directory?
Weekly logs are a pain (because it's non-trivial to calculate which week you are in). If you want to move rather than copy the files, then you can just use *.LOG because there won't be any old logs there, but there can be issues there too. > 2) Is there a way to have analog to delete the log file once it is done? Analog won't delete anything. You can have the script that calls Analog delete files when Analog is done, but analog won't do it for you. > 3) Does anyone have a good suggestion on how to readily accomplish this > maybe using a different approach? There's nothing really wrong with your approach, but I'd give some thought to using daily logs rather than weekly logs. Do you just plan to publish the previous weeks Log report? What about the last month, or the last year? Also bear in mind that some customers will not want this information made public, and some will. 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/analog-help@lists.isite.net/ | http://lists.isite.net/listgate/analog-help/archives/ | http://www.tallylist.com/archives/index.cfm/mlist.7 +------------------------------------------------------------------------
