From: Reuben Farrelly <reuben-linux@reub.net>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.4.20-aa and LARGE Squid process -> SIGSEGV
Date: Sat, 21 Dec 2002 20:17:42 +1100 [thread overview]
Message-ID: <5.2.0.9.2.20021221201604.03a16110@tornado.reub.net> (raw)
In-Reply-To: <20021221090642.GD31070@charite.de>
[Forwarded for the purposes of continuity, Robert is not on lkml]
>Subject: Re: 2.4.20-aa and LARGE Squid process -> SIGSEGV
>From: Robert Collins <robertc@squid-cache.org>
>To: Reuben Farrelly <reuben-linux@reub.net>
>Cc: Ralf Hildebrandt <Ralf.Hildebrandt@charite.de>
>X-Mailer: Ximian Evolution 1.0.8
>Date: 21 Dec 2002 20:12:21 +1100
>
>On Sat, 2002-12-21 at 20:06, Ralf Hildebrandt wrote:
> > * 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?
>
>In general, it can.
>Folk run it with up to 2Gb with no special options on linux, all the
>time.
>
>Have you tried asking on the *right* list?
>Or running it under gdb?
>Or getting a stacktrace?
>
>SEGSIGV does *not* mean out of memory, you *may* have hit a genuine bug,
>but it *not* due to squid handling a failed malloc wrongly.
>
>Rob
prev parent reply other threads:[~2002-12-21 9:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-20 11:48 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
2002-12-21 9:17 ` Reuben Farrelly [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=5.2.0.9.2.20021221201604.03a16110@tornado.reub.net \
--to=reuben-linux@reub.net \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®