Re: argus client -S option
Carter Bullard <carter <at> qosient.com>
2008-06-02 17:21:00 GMT
Hey CS Lee,
Well lots of things in your email.
All the ra* programs use the same code to attach and read data, so
it is unlikely that there is a problem specific to a given ra* program
when it relates to attaching to remote argi sources.
Try compiling with debug support and running with something like "-D5".
That should tell you enough, I suspect, to see what is going on.
The polling is to see if the remote source is there and running, but
we turned printing management records off by default, so you may need
to turn on the "RA_PRINT_MAN_RECORDS" for the polling to appear to
As to ratop(), I need a bit more detail than you have provided to understand
what could be the problem. There are a lot of potential gotchas with curses
based programs on many platforms, so I'll need stuff like the output of the
./configure run, to see what curses did it find, etc....
Hope all is most excellent,
On Jun 2, 2008, at 11:47 AM, CS Lee wrote:
Been a while since I was active here ... hopefully everyone is doing well ;]
I'm using argus 3 release now.
One question, can anyone connect to argus probe in real time using argus client tools except ra. For example -
argus -B 127.0.0.1 -P 561 -i eth1
ra -S 127.0.0.1:561
The ra has no problem, but when I use racluster or other client tools, it seems no output is printed in stdout once it is connected to the argus.
On the other hand, I try the -M poll, it doesn't seem that the client is attaching to the server and exit immediately.
And when i use ratop on freebsd 7, no problem when attaching to the argus probe, but this is not the case on ubuntu gutsy.