argus-2.0.6.beta.10

[Carter Bullard]

I hate it when this happens.  Runs fine on RedHat, in all
combinations of parameters that I can think of.

Ok, the difference here is that we're running getopt()
twice, first to pull out any "-F" options, in order
to decide if we should or shouldn't open /etc/argus.conf,
and then second to parse out the rest of the options.

The source input processor, uses optind as the index
for the start of the commandline filter, and in your
example it should be pointing at the NULL that should
be at the end of argv.

Is it possible that the BSD's are doing something
funky with argv, and not putting a NULL at the end?

If you don't mind, could you debug argus, by
touching ".devel" in the root directory, re-configuring
and recompiling, and then break in ArgusCopyArgv,
to see what the optind is and to see what it thinks
argv should be?

Carter





> -----Original Message-----
> From: owner-argus-info at lists.andrew.cmu.edu 
> [mailto:owner-argus-info at lists.andrew.cmu.edu] On Behalf Of 
> Peter Van Epp
> Sent: Monday, July 14, 2003 2:28 PM
> To: argus-info at lists.andrew.cmu.edu
> Subject: Re: argus-2.0.6.beta.10
> 
> 
> 	Hmmm, in addition to the various compile errors and for 
> the first time
> in memory :-) it looks like the compiled code is also broken 
> (or the defaults
> have changed in such a way I need a config file now). When I 
> try and run
> argus_bpf on any of the BSD systems I get a parse error like 
> this (this one
> happens to be Mac OS 10 the others are the same):
> 
> [test4:vanepp/argus-2.0.6.beta.10/bin] vanepp# ./argus_bpf -w 
> argus.out
> argus_bpf[2673]: ArgusInputFilter "argus_bpf argus.out" parse error
> 
> Peter Van Epp / Operations and Technical Support 
>