argus-2.0.0q

[Carter Bullard]

Gentle people,

ftp://qosient.com/dev/argus/argus-2.0/argus-2.0.0q.tar.gz
is available.  In addition to some basic and esoteric bug
fixes, the highlight of this release is .argusrc and .rarc
resource file support.  Please see ./examples/.argusrc and
./examples/.rarc to see how they work.

The big deal is that you can specify your own time
format.  Please give it a try.  The RA_FIELD_DELIMITER
support has not been implemented, but its there to be
able to do what we've all been waiting for, comma separated
files and the like.  I'll have that support tomorrow.

The path used by argus and all the ra* clients to
these files is currently set as:

   $ARGUSHOME/.[argus ra]rc; $HOME/.[argus ra]rc

I will add ./.[argus ra]rc in the next release.

Unfortunately Russell's mail below arrived too late to
have any impact on my stab at .rc support, so take this
stab as just a first effort.

Please have a test,

Carter

Carter Bullard
QoSient, LLC
300 E. 56th Street, Suite 17A
New York, New York  10022

carter at qosient.com
Phone +1 212 813-9426
Fax   +1 212 813-9426


-----Original Message-----
From: r.fulton at auckland.ac.nz [mailto:r.fulton at auckland.ac.nz]
Sent: Monday, October 16, 2000 4:23 PM
To: Carter Bullard
Subject: Re: RE: RE: RE: argus-2.0.0p



On Mon, 16 Oct 2000 08:31:44 -0400 Carter Bullard <carter at qosient.com> 
wrote:

> I think the .argusrc file is a good idea possible for
> 2.0.0.  I also am pretty tired of all the typing ;o)
> I'll make a first stab at it today.
> 

Great, can I suggest different sections for each client -- like the 
dreaded MS .ini format:

[argus]
switches = '-P666 -d30 -w current'
[ra] 
switches = '-znc -U0 -L-1'

or possibly

[argus]
Port = 666 
Detail = 30 
Write = current
[ra] 
Status_bytes = yes
no_name_lookup = yes
Time_precision = 0
Labels = -1

So the various clients only read the bits relevant to them. 

Hmmm... how about having a section at the start of the -F <file> in 
which you can specify parameters.  

so on startup the client reads argusrc file, command line arguments and 
then processes -F file.  This would mean that things specified in the 
-F<file> would override command line which may be a little counter 
intuitive ??

The other questions is what search path to use for the argusrc?  I 
would suggest

current dir: home dir: ARGUSDIR

I seem to remember that you said that you intended to have a/some 
Enviroment variables.

> We are using '_' to separate src and dst flags with
> the Zflag, so we are consistent, whether its right or
> not ;o)

Yes, I found the relevant bit of email about half an hour later!

> 
> I am going to put in an ARGUS_DELIMITER flag in the
> .argusrc, as I see a need to support either tab or comma
> separated files.  The '_' will be an inter-field delimiter
> and won't change based on this flag.

Sounds great.

On the racount front, I'll set aside an hour or so this afternoon to 
have a good poke around with gdb and see if I can figure out what is 
going on.  It has to be something BDS specific. I'll also compile 2.0 
on Linux and copy the file there for a comparision.

Will keep you posted.

Cheers, Russell.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist1.pair.net/pipermail/argus/attachments/20001016/fbe65e43/attachment.html>