diff options
author | Pablo Neira Ayuso <pablo@netfilter.org> | 2011-02-25 18:05:59 +0100 |
---|---|---|
committer | Pablo Neira Ayuso <pablo@netfilter.org> | 2011-02-25 18:57:28 +0100 |
commit | e7e229fd66454a11317b2386948ff2055903e7ea (patch) | |
tree | 849604620f0f8f1f42de9dd09a49d7a3b34914ac /doc | |
parent | ff196ff7ff31e7dc38260bd54d5e0e9e99bf3839 (diff) |
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 <pablo@netfilter.org>
Diffstat (limited to 'doc')
-rw-r--r-- | doc/sqlite3.txt | 7 | ||||
-rw-r--r-- | doc/ulogd.sgml | 11 |
2 files changed, 10 insertions, 8 deletions
diff --git a/doc/sqlite3.txt b/doc/sqlite3.txt deleted file mode 100644 index 97e8bc9..0000000 --- a/doc/sqlite3.txt +++ /dev/null @@ -1,7 +0,0 @@ -XXX: This has to go in ulogd.sgml, later. - -To create the database file, you have to: -$ sqlite3 file.db < sqlite3.table - -To check that we are logging stuff into it correctly: -sqlite3 ulogd.sqlite3db "SELECT * from ulog" 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. <p> You may want to have a look at the file '<tt>doc/sqlite3.table</tt>' 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. + +<p> +To create the database file with the tables, you have to invoke the following +command: <tt>sqlite3 ulogd.sqlite3db < sqlite3.table</tt> + +<p> +To check that we are logging stuff into it correctly: +sqlite3 ulogd.sqlite3db "SELECT * from ulog_ct" <p> The module defines the following configuration directives: |