[lkml]   [2002]   [Dec]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: 2.4.20-aa and LARGE Squid process -> SIGSEGV
* Reuben Farrelly <>:

> 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

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)
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?"

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:31    [W:0.038 / U:4.456 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site