From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Patrick McHardy <kaber@trash.net>
Cc: Andreas Lundin <lunde@dreamhosted.se>,
netfilter-devel@lists.netfilter.org
Subject: Re: ulogd large file support
Date: Tue, 19 Jun 2007 15:57:28 +0200 [thread overview]
Message-ID: <4677E0C8.2000309@netfilter.org> (raw)
In-Reply-To: <4677DBC8.1090401@trash.net>
Patrick McHardy wrote:
> Andreas Lundin wrote:
>> ulogd seems to be missing large file support. Here is a simple patch
>> to make configure handle it, but there is a line that is commented in
>> Rules.make.in which will prevent the option to be used during compile
>> time (search for @DEFS@ in Rules.make.in).
>>
>> I compiled ulogd-1.24 with -D_FILE_OFFSET_BITS=64 and it can now write
>> to log files larger than 2G on my system.
>
> Applied, thanks. I've ran into this a couple of days ago with ulogd2,
> so I've applied your patch there as well.
JFYI: I just applied another patch on top of it to check for autoconf >=
2.50 (required by AC_SYS_LARGEFILE), removed autogenerated
libipulog/Makefile from SVN and uncomment the @DEFS@ line in
Rules.make.in to pass -D_FILE_OFFSET_BITS=64 at compilation stage.
I'm still working with Marius Tomaschewski on several pending patches.
We'll release a new version once we've finish with them.
--
The dawn of the fourth age of Linux firewalling is coming; a time of
great struggle and heroic deeds -- J.Kadlecsik got inspired by J.Morris
next prev parent reply other threads:[~2007-06-19 13:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-19 13:30 ulogd large file support Andreas Lundin
2007-06-19 13:36 ` Patrick McHardy
2007-06-19 13:57 ` Pablo Neira Ayuso [this message]
2007-06-19 13:59 ` Patrick McHardy
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=4677E0C8.2000309@netfilter.org \
--to=pablo@netfilter.org \
--cc=kaber@trash.net \
--cc=lunde@dreamhosted.se \
--cc=netfilter-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.