ulogd - maximum polling time interval - without risk of losing data

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

Your help would be much appreciated.

I'm using ulogd(NACCT) with polling. If I just use polling based
logging without event based logging, are there any chances that I may
some connection data?
What could be the maximum polling interval value in which I dont miss
the NACCT data?
For example, if I set polling interval as 600s, there are chances I
may some NACCT data, since some timeout values are less than that(like
net.netfilter.nf_conntrack_tcp_timeout_last_ack = 30). If the
connection destroys before logging, then its a miss.

net.netfilter.nf_conntrack_tcp_timeout_close has a timeout of 10
seconds. My guess is I should have polling interval less than this to
avoid missing of any data. Is it correct?


Thanks & Regards,
--
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Netfitler Users]     [LARTC]     [Bugtraq]     [Yosemite Forum]

  Powered by Linux