On Fri, 10 Nov 2000, Kevin Hemenway wrote:
>
> Ahh... it may have, but cron redirects that particular script's STDOUT to
> the bitbucket, since the log running is also combined with some other noisy
> log type of junky things...
>
stderr, not stdout. Binning stderr is BAD! If you have to do it for some
programs, do it on a line-by-line basis, not on the whole script.
> a) cron the weekly reports, make a cache.
> b) cron the overall, removing CACHEOUTFILE from my overall config?
>
Right. Make a cache file from each logfile. Make the reports from the cache
files.
> And to recover correctly in my overall, I should delete all my cache files
> and my old overall report? Without the logfiles, is there anyway to
> magically rerun a correct overall (I know, I know, but I'm praying really,
> really hard!).
>
No, sorry. Well, not unless you can work out exactly how you made them, and
write another program to remove all the double counting etc.
--
Stephen Turner http://www.statslab.cam.ac.uk/~sret1/
Statistical Laboratory, Wilberforce Road, Cambridge, CB3 0WB, England
"The new operating system will recover more easily from system crashes."
(Microsoft, aiming high with Windows Millennium)
------------------------------------------------------------------------
This is the analog-help mailing list. To unsubscribe from this
mailing list, send mail to [EMAIL PROTECTED]
with "unsubscribe" in the main BODY OF THE MESSAGE.
List archived at http://www.mail-archive.com/[email protected]/
------------------------------------------------------------------------
