Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Atilla <theatilla@gmail.com>
To: netfilter@lists.netfilter.org
Subject: Re: Weird behaviour when compiling iptables
Date: Tue, 25 Jan 2005 16:24:32 +0200	[thread overview]
Message-ID: <b53c932d05012506247bd8ed@mail.gmail.com> (raw)
In-Reply-To: <b53c932d0501240507143cd370@mail.gmail.com>

Ok, I got some progress (i think). I got the 2.6.10 kernel, and
compiled it and replaced the old one with it. With and without
patching the kernel and the iptables source i get the same thing:
"Making dependencies, please wait..." and it stays there. CPU usage is
100%, with make forking to cpp0 and cc processes all the time - at
least that's what i got from what TOP shows. I ran STRACE on this -
it's a loooong sequence of things i don't understand but at least i
know it doesn't hang - ot loops continuously doing something.

Now - I'm doing this on a Pentium II 400mhz machine with 128RAM and
1GB swap. The ram usage is VERY low when doing this. I don't know how
much the process should take but I left it yesterday for hours and it
was still doing the same thing. A kernel compile, for example, takes
it like 1/2 an hour.  Oh - and iptables 1.3.0 does the same thing -
"making dependencies, please wait... " - i thought it might do some
difference - it didn't.  So i'm stuck at this point. Apparently i did
something to the system, but i can't figure out what. I haven't been
changing any important things like compilers and libraries and the
such, that's for sure.

I'm kind of new to all this but I figure I'm way too stuck on this
one. Any further clues are highly appreciated.


      reply	other threads:[~2005-01-25 14:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-24 13:07 Weird behaviour when compiling iptables Atilla
2005-01-25 14:24 ` Atilla [this message]

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=b53c932d05012506247bd8ed@mail.gmail.com \
    --to=theatilla@gmail.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