On 08/21/2013 02:44 PM, Kevin Branch wrote:
I am hoping to switch my existing traffic recording systems from using daemonlogger
> to netsniff-ng. They make hourly capture files that start at the top of the hour and > end and the end of the hour. Daemonlogger's default behavior for handling time-based > intervals is to roll over at the top of the interval in alignment with the time of day > so a "1 hour" interval would pick up traffic from 8:00-8:59, 9:00-9:59, etc... always > rotating at the exact top of the hour even if that means the first interval is much > shorter because the program is started in the middle of an hour. Based on my current > experimentation, it appears netsniff-ng aligns its intervals with the exact start time > of the program, so if I start an hourly interval capture at 8:35, all capture files will > start at 35 minutes after the hour. I can't guarantee that my traffic recording system > will always be started at the exact top of the hour, so could you consider making an > option in netsniff-ng to rotate on even
time intervals, perhaps --even-intervals?
Great idea. We could indeed do something about that. We will put this on the list for rc4. Thanks ! -- You received this message because you are subscribed to the Google Groups "netsniff-ng" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
