From owner-freebsd-questions Sun Apr 16 22:45:34 2000 Delivered-To: freebsd-questions@freebsd.org Received: from www.ozler.com (asy57.as154.sol.superonline.com [212.252.154.57]) by hub.freebsd.org (Postfix) with ESMTP id 6961F37B5F8 for ; Sun, 16 Apr 2000 22:45:22 -0700 (PDT) (envelope-from ertank@ozlerplastik.com) Received: from ozlerplastik.com (ertan [192.168.0.20]) by www.ozler.com (8.9.3/8.9.3) with ESMTP id IAA79853 for ; Mon, 17 Apr 2000 08:48:58 +0300 (EEST) (envelope-from ertank@ozlerplastik.com) Message-ID: <38FAA473.19B99C62@ozlerplastik.com> Date: Mon, 17 Apr 2000 08:43:15 +0300 From: Ertan Kucukoglu Organization: =?iso-8859-9?Q?=D6zler?= Plastik San. ve Tic. A.S. X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: tr,en MIME-Version: 1.0 To: questions@FreeBSD.org Subject: Can't run squid with leased line (solved partly) Content-Type: text/plain; charset=iso-8859-9 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, Previous week I sent a message explaining my problem about using squid with a leased line. Now, I find out something. When I looked at squid log files deeply I see that whenever a request comes squid child process dies with the segmentation fault error and another squid child process is starting automatically by main process. The mentioned squid was a 2.3STABLE2. I downloaded it from squid web site and compiled with '--prefix=/squid' parameters. I'm using FreeBSD 4.0-RELEASE. I also have some FreeBSD 3.5 and 3.3 machines. I also use squid2.3S1 on them as the same way I do in 4.0, but 4.0 seg faulting. Then I tried to use squid-2.3.tgz from the ports collection and viola, it runs. Now, I wonder what made the squid die and what parameters used when compiling the squid-2.3.tgz in the ports collection. Regards, -- Ertan Kucukoglu ertank@ozlerplastik.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message