From owner-freebsd-current Sat May 2 03:37:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA02301 for freebsd-current-outgoing; Sat, 2 May 1998 03:37:48 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from saten.dyn.ml.org (197.ppp3.gulftel.com [208.222.58.197]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA02295 for ; Sat, 2 May 1998 03:37:41 -0700 (PDT) (envelope-from lists@saten.dyn.ml.org) Received: from localhost (lists@localhost) by saten.dyn.ml.org (8.8.8/8.8.5) with SMTP id FAA00569; Sat, 2 May 1998 05:35:55 -0500 (CDT) Date: Sat, 2 May 1998 05:35:54 -0500 (CDT) From: Phillip Salzman To: Andrew cc: freebsd-current@FreeBSD.ORG Subject: Re: httpd caught SIGBUS????? In-Reply-To: <3.0.32.19980502200705.006b8c6c@iaccess.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 2 May 1998, Andrew wrote: > hey, > > I just upgraded to the latest kernel which i CVSUP from freebsd.org and i > it seems to have caused a problem with apache. > I have apache running on port 464 for the cachemgr.cgi in squid. > Everything is fine when i start httpd, but when i try to connect to port > 464 or even when i try to telnet to that port, it says this: [snip] Yep, its the virtual memory. CVSup back to whatever date it was your old kernel was from if this bugs you. As in a previous post, Dyson is working on it. To go back to some other date on the sources, add this to your supfile: *default date=yr.mm.dd.hh.mm.ss - i did 98.04.20.00.00.00, but I just remembered that the Linux emu. was broken, and x11amp just core dumped on signal 10 for me... I do not know if it was broken on that date or not - maybe my hardware is b0rked. Phillip Salzman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message