rasql with gzipped files

[carter at qosient.com]

Hey Terry,
The "-M " option  is designed for this, and I could easily add your suggestion to that option.

Carter 

Sent from my Verizon Wireless BlackBerry

-----Original Message-----
From: Terry Burton <tez at terryburton.co.uk>
Date: Wed, 21 Apr 2010 21:44:23 
To: carter<carter at qosient.com>
Cc: Argus<argus-info at lists.andrew.cmu.edu>
Subject: Re: [ARGUS] rasql with gzipped files

On Wed, Apr 21, 2010 at 9:15 PM,  <carter at qosient.com> wrote:
> So I'll add the scratch path configuration variable to .rarc.  Too esoteric to put a command line option?

Hey Carter,

I agree that perhaps this is too exotic for a new command line parameter.

However, have you ever considered configuring the daemons and clients
by reading state progressively from a variety of contexts using a
well-defined naming convention. Perhaps as follows, allowing
subsequent contexts to override values set in the former:

compiled in defaults
rarc
environment varliables (e.g. export $ARGUS_GENERATE_MAC_DATA=yes)
existing short command line parmaters (e.g. -m)
new long command line parameters (e.g. -o ARGUS_GENERATE_MAC_DATA=yes)

This would provide a very flexible and consistent framework for
configuration. In my case, wherever possible I run my clients with the
-X option (ignore rarc) and pass the configuration via command line
parameters. (This is my personal preference and since all of this is
meta to the core Argus functionality I can well understand if you
disagree or consider it not worth the effort!).

> I'll also need to add the database to the path.
> Should have it by the end of the week.

That's great - thanks!


Terry


> -----Original Message-----
> From: carter at qosient.com
> Date: Wed, 21 Apr 2010 12:30:02
> To: Terry Burton<tez at terryburton.co.uk>; <argus-info-bounces+carter=qosient.com at lists.andrew.cmu.edu>; Argus<argus-info at lists.andrew.cmu.edu>
> Subject: Re: [ARGUS] rasql with gzipped files
>
> Yes, this is an issue.  Several ways of solving this but, hard to say they are all elegant.  If we think of uncompressed files as local cached files, then the solution could deal with remote files as well.
>
> We can specify an ARGUS_SCRATCHPATH, and uncompress the file(s) as:
>
>  ARGUS_SCRATCHPATH/hostname/SQL_FILENAME
>
>  We can look here first and if not here do our fetching/decompression there.
>
> Just need to reclaim the disk space at sometime.
>
> Carter
>
>
> ------Original Message------
> From: Terry Burton
> Sender: argus-info-bounces+carter=qosient.com at lists.andrew.cmu.edu
> To: Argus
> Subject: [ARGUS] rasql with gzipped files
> Sent: Apr 21, 2010 6:19 AM
>
> Hi Carter,
>
> I've hit a problem that when rasql reads gzipped files, it first
> attempts to unzip the files into their own directory. In several
> setups this results in permissions issues since the user running rasql
> would require write access to the primitive flow data directories
> which may not be desirable. It would be nice to be able to specify an
> alternative location for the scratch space.
>
>
> Thanks for your great work!
>
> Terry