Anton wrote: > Just some extra results, > > seems DB drivers does such a difference, since while logging > to LOGEMU (only) target - I've go result which looks true. > But - If I enable DB logger - results in DB and LOGEMU - > are the same. Looks like DB transfers makes ULOG to not > accept packets from kernelspace The problem is netlink that cannot back off. Netlink is the underlying communication subsystem that we use to communicate kernel with usepace space. Since Netlink is unreliable, some log messages can vanish under heavy load. I guess that database insertions consumes lots of CPU resouces. Thus, doing online database logging in a scalable manner turns really hard. Instead, if you need scalability, I'd suggest to use logemu or whatever plain text logging facility and then convert it to a database *offline* if you really need advanced queries. -- "Los honestos son inadaptados sociales" -- Les Luthiers -- 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
