Re: [cobalt-users] Has anyone used wusage on Linux/MIPS?

["J. Masterson" <masterson@xxxxxxxxxxxx>]

I used to administer our Wusage6 and later 7 on an Intel-based Linux box
and a BSDi3 (and later 4) box.

I really didnt use their web interface at all, except to generate one
sample report. Thereafter, I set up new reports with a simple perl
script which created a new config file for the site as well as appended
the name of that config file to a file that listed all config files to
be analyzed (we had several hundred).

Then I had a cron job fire off in the pre-dawn hours which would read in
the list and sequentially use system() to start up wusage for each
config file (with the '-c' argument).

That's how we did it, and it worked.


Addendum:
We had a problem with Wusage7 complaining "Ran out of memory!" when
crunching larger logfiles. It turned out after much trial and error
(this according to my successor; I've changed jobs) that the problem was
not RAM, but rather disk space. Apparently Wusage7 writes gobs of
temporary files while it runs... these were filling up the hard disk and
causing it to choke.


-- 
John Masterson
Web Developer
WAM!NET Missoula
masterson@xxxxxxxxxxxx



Dave Small wrote:
> 
> Hi all.
> 
> Has anyone out there used a recent version of wusage under Linux/MIPS? I'm
> not having problems with getting it up and running (and the output is very
> very thorough and well-done), but I don't seem to be able to find any way of
> scheduling updates - ideally I'd like it to run at 4am every day. I know
> that getting the wusage program up is a cron job, but once it's up, I need
> to set something up inside wusage to do the updates.
> 
> Has anyone had success in running wusage daily/weekly automatically? (Or is
> this a feature that gets unlocked when the product is registered?)
> 
> Thanks
> Dave Small
> 
> _______________________________________________
> cobalt-users mailing list
> cobalt-users@xxxxxxxxxxxxxxx
> http://list.cobalt.com/mailman/listinfo/cobalt-users