ra 3.0 timerange broken?

Jesper Skou Jensen jesper.skou.jensen at uni-c.dk
Thu Mar 12 05:29:12 EDT 2009


Hi guys,

I think there is a bug in the 3.0 ra client's timerange.

I would expect the same output from the two commands below, but that's 
not the case.

ra -r logfile.gz -t 10:01-10:02
reports no output

ra -r logfile.gz -t 2009/03/11.10:01-10:02
reports all the sessions as expected


-- 

   Jesper S. Jensen
UNI-C - Århus, Danmark



More information about the argus mailing list