From: Ralf Hildebrandt <Ralf.Hildebrandt@charite.de>
To: Reuben Farrelly <reuben-linux@reub.net>
Cc: Ralf Hildebrandt <Ralf.Hildebrandt@charite.de>,
linux-kernel@vger.kernel.org,
Robert Collins <robertc@squid-cache.org>
Subject: Re: 2.4.20-aa and LARGE Squid process -> SIGSEGV
Date: Sat, 21 Dec 2002 10:06:42 +0100 [thread overview]
Message-ID: <20021221090642.GD31070@charite.de> (raw)
In-Reply-To: <5.2.0.9.2.20021221191530.02ade850@tornado.reub.net>
* Reuben Farrelly <reuben-linux@reub.net>:
> No, squid is not br0ken in this fashion. If squid cannot be allocated
> enough memory by the system, it logs a message and _dies_. Relevant files
> to look at in your squid source are squid/lib/util.c for xcalloc() and
> xmalloc().
Why can't squid allocate more than 1GB on a system with 2GB RAM?
> Aside from this, if squid ever does get to the point of swapping, it is
> misconfigured and your performance has just gone to hell anyway... (see
> the FAQ at www.squid-cache.org)
It's not swapping. That's the whole point. We have 2GB and can use at
most 1GB for Squid.
--
Ralf Hildebrandt (Im Auftrag des Referat V a) Ralf.Hildebrandt@charite.de
Charite Campus Mitte Tel. +49 (0)30-450 570-155
Referat V a - Kommunikationsnetze - Fax. +49 (0)30-450 570-916
Microsoft: "Where do you want to go today?"
Linux: "Where do you want to be tomorrow?"
BSD: "Are you guys coming, or what?"
next prev parent reply other threads:[~2002-12-21 8:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-20 11:48 2.4.20-aa and LARGE Squid process -> SIGSEGV Ralf Hildebrandt
2002-12-20 22:37 ` J.A. Magallon
2002-12-20 22:57 ` Ralf Hildebrandt
2002-12-21 0:13 ` J.A. Magallon
2002-12-21 7:52 ` Ralf Hildebrandt
2002-12-21 8:28 ` Reuben Farrelly
2002-12-21 9:06 ` Ralf Hildebrandt [this message]
2002-12-21 9:17 ` Reuben Farrelly
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=20021221090642.GD31070@charite.de \
--to=ralf.hildebrandt@charite.de \
--cc=linux-kernel@vger.kernel.org \
--cc=reuben-linux@reub.net \
--cc=robertc@squid-cache.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.