From: Jason Opperisano <opie@817west.com>
To: netfilter@lists.netfilter.org
Subject: Re: FC2 + PowerEdge 2650 + smp kernel + iptables rules loading slow
Date: Tue, 7 Dec 2004 12:55:46 -0500 [thread overview]
Message-ID: <20041207175546.GA26307@bender.817west.com> (raw)
In-Reply-To: <41B5DBB3.1030009@net-m.de>
On Tue, Dec 07, 2004 at 05:34:59PM +0100, Iulian Topliceanu wrote:
> Hi,
>
> I recently noticed the following:
>
> OS: FC2
> Kernel: 2.6.8smp and 2.6.8
> Hardware: Dell PowerEdge with 2 x 2.8 CPUs, 2 GB RAM etc.
> iptables version: iptables-1.2.9-2.3.1
isn't the latest FC2 kernel 2.6.9-1.6? i would go ahead and try that,
as i had nothing but problems with the 2.6.8 FC2 kernels.
did you have this problem with 2.6.7 as well?
-j
--
"Here we have an ordinary square.
Whoa! Slow down egghead!"
--The Simpsons
next prev parent reply other threads:[~2004-12-07 17:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-07 16:34 FC2 + PowerEdge 2650 + smp kernel + iptables rules loading slow Iulian Topliceanu
2004-12-07 16:42 ` Ugo Bellavance
2004-12-07 16:47 ` Ugo Bellavance
2004-12-07 17:55 ` Jason Opperisano [this message]
2004-12-07 18:01 ` Iulian Topliceanu
2004-12-08 13:49 ` a.ledvinka
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=20041207175546.GA26307@bender.817west.com \
--to=opie@817west.com \
--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