lkml.org 
[lkml]   [2002]   [Dec]   [21]   [last100]   RSS-feed
Views: [more markup]  [less markup]  [headers]  [forward] 
 
Messages in this thread
Complete thread (EXPERIMENTAL)
/
DateSat, 21 Dec 2002 10:06:42 +0100
FromRalf Hildebrandt <>
SubjectRe: 2.4.20-aa and LARGE Squid process -> SIGSEGV
Digg This
* 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?"

\
ISP Services
Valid XHTML 1.0!\ /
Valid CSS! Last update: 2005-03-22 12:31    [W:1.335 / U:0.030 seconds]
©2003-2005 Jasper Spaans