From e7e229fd66454a11317b2386948ff2055903e7ea Mon Sep 17 00:00:00 2001 From: Pablo Neira Ayuso Date: Fri, 25 Feb 2011 18:05:59 +0100 Subject: sqlite3: remove automatic creation of table `daily' This patch removes the creation of the `daily' table. Now, we assume that the table that we use are created before launching ulogd2. This code is broken because you have to specify in the configuration file that the table used is `daily', otherwise this `daily' table is created and dropped during the daemon starting, but not used. Moreover, the code explicit shows a message that it says: /* FIXME make this configurable */ So, I think that this patch is the way to go :-). This patch also documents the table creation in ulogd.sgml Signed-off-by: Pablo Neira Ayuso --- doc/ulogd.sgml | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) (limited to 'doc/ulogd.sgml') diff --git a/doc/ulogd.sgml b/doc/ulogd.sgml index 8e31fb6..547b56a 100644 --- a/doc/ulogd.sgml +++ b/doc/ulogd.sgml @@ -576,7 +576,16 @@ unsigned integer into the table.

You may want to have a look at the file 'doc/sqlite3.table' as an example table including fields to log all keys from ulogd_BASE.so. Just delete -the fields you are not interested in, and create the table. +the fields you are not interested in, and create the table. This file contains +two tables, one for packet-based logging and another for flow-based logging. + +

+To create the database file with the tables, you have to invoke the following +command: sqlite3 ulogd.sqlite3db < sqlite3.table + +

+To check that we are logging stuff into it correctly: +sqlite3 ulogd.sqlite3db "SELECT * from ulog_ct"

The module defines the following configuration directives: -- cgit v1.2.3