From: "Steve Melo" <smelo@communitytrust.ca>
To: netfilter@lists.netfilter.org
Subject: ULOGD and invalid timestamps
Date: Thu, 9 Sep 2004 12:30:32 -0400 [thread overview]
Message-ID: <00cd01c4968a$53c10b30$3c01a8c0@tftpd> (raw)
Greetings list,
I'm using the ulogd to log information and everything works great except
that everything that gets logged has a timestamp of "Dec 31 19:00:00". I
would like to have the correct timestamp.
Here is my setup:
Debian Linux w/2.6.7-1-686 kernel (binary install)
ulogd Version 1.02
iptables v1.2.9
Here is my /etc/ulogd.conf:
# netlink multicast group (the same as the iptables --ulog-nlgroup param)
nlgroup 1
# logfile for status messages
logfile /var/log/ulog/ulogd.log
# loglevel: debug(1), info(3), notice(5), error(7) or fatal(8)
loglevel 5
# socket receive buffer size (should be at least the size of the
# in-kernel buffer (ipt_ULOG.o 'nlbufsiz' parameter)
rmem 131071
# libipulog/ulogd receive buffer size, should be > rmem
bufsize 150000
# ulogd_BASE.so - interpreter plugin for basic IPv4 header fields
# you will always need this
plugin /usr/lib/ulogd/ulogd_BASE.so
plugin /usr/lib/ulogd/ulogd_LOCAL.so
#
# ulogd_LOGEMU.so - simple syslog emulation target
#
# where to write to
syslogfile /var/log/ulog/syslogemu.log
# do we want to fflush() the file after each write?
syslogsync 1
# load the plugin
plugin /usr/lib/ulogd/ulogd_LOGEMU.so
#
# ulogd_OPRINT.so: file for packet dumping
#
# where to write the log
dumpfile /var/log/ulog/pktlog.log
# load the plugin (remove the '#'if you want to enable it
plugin /usr/lib/ulogd/ulogd_OPRINT.so
next reply other threads:[~2004-09-09 16:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-09 16:30 Steve Melo [this message]
2004-09-10 13:53 ` ULOGD and invalid timestamps Jason Opperisano
-- strict thread matches above, loose matches on Subject: below --
2004-09-10 13:41 Piszcz, Justin Michael
2004-09-10 14:48 ` Steve Melo
2004-09-10 15:23 Piszcz, Justin Michael
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='00cd01c4968a$53c10b30$3c01a8c0@tftpd' \
--to=smelo@communitytrust.ca \
--cc=netfilter@lists.netfilter.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox