another ramon buglet

[Carter Bullard]

Hey Peter,
   All ra*() programs share the same main() routine,
so they all will accept the same options on the command line.
-d option here is not used by the client, but the main
routine still sets the global ra* option.

   I can go through and have all the programs look for
incidental flags, i.e. flags that aren't intended for them,
but then the .rarc configurations would break, and so that's
not going to work.

   Can we tolerate this side effect?

   So what's up with stdout on FreeBSD?  Is there a work
around?

Carter

Carter Bullard
QoSient, LLC
300 E. 56th Street, Suite 18K
New York, New York  10022

carter at qosient.com
Phone +1 212 588-9133
Fax   +1 212 588-9134

> -----Original Message-----
> From: Peter Van Epp [mailto:vanepp at sfu.ca]
> Sent: Friday, February 16, 2001 1:07 AM
> To: Carter Bullard
> Subject: another ramon buglet
> 
> 
> 	Looks like there is a problem with stdout on FreeBSD and there 
> looks to be an error in option processing too. This should be 
> illegal (but
> isn't):
> 
> 227: vanepp_fraser% !221
> ./ramon -d6 -M TopN -N4 -n -c -r ../../argus.2001.02.15.21.30.00.gz
> 15 Feb 01 21:19:41     ip     142.58.35.6          339604   
> 246791    484976026
>    15052086    CON
> ...
> 
> ./ramon -D6 etc
> 
> sets debug on as expected, but the -d should (I think) give 
> help and doesn't
> because there doesn't seem to be a -d option. Since the data 
> file being 
> processed is from FreeBSD it looks like there is a problem 
> with ramon on 
> FreeBSD (since Solaris ramon prints the file fine).
> 
> Peter Van Epp / Operations and Technical Support 
> Simon Fraser University, Burnaby, B.C. Canada
> 
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist1.pair.net/pipermail/argus/attachments/20010216/fddf85bc/attachment.html>