Date: Wed, 14 Jun 2006 18:24:55 -0500 From: "Scot Hetzel" <swhetzel@gmail.com> To: "Robert Leftwich" <freebsd@rtl.fmailbox.com> Cc: freebsd-amd64@freebsd.org Subject: Re: Runaway memory usage on 6.1/amd64 Message-ID: <790a9fff0606141624t678e07ddl20d5bdac353aaf1@mail.gmail.com> In-Reply-To: <448F6FCF.6060700@rtl.fmailbox.com> References: <448F304A.1060204@rtl.fmailbox.com> <448F6FCF.6060700@rtl.fmailbox.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 6/13/06, Robert Leftwich <freebsd@rtl.fmailbox.com> wrote: > Robert Leftwich wrote: > > > > I've tried a vanilla 6.1 install (straight off the CD, no cvsup) which > > installs Postgres 8.1.3 and Python 2.4.2, as well as cvsup to the latest > > 6.1 release and updating everything to the latest ports (PG8.1.4 and > > Python 2.4.3) without success. > > The same occurs on 6.1 stable, if anyone is interested. > If you have the cvs repository, you could checkout a 6.1 RC 1 source tree and see if that gives you a stable system. cvs -d /home/ncvs co src -rRELENG_6 -D "2006-04-08 14:42:23 UTC" If you already have a checked out source tree use "update" instead of "co". According to a message from Scott Long, 6.1 Beta 4 was made available on Mar 14, 2006 22:30:25 -0700. Note: This is the date of the announce message not the time the source was checked out from the cvs repository, though it may get you close enough to the 6.1 Beta 4. After you get back to the stable 6.1 beta 4, you might want to try doing a binary search of the sources to find out what cvs checked out date causes the problem to occurs. Scot -- DISCLAIMER: No electrons were mamed while sending this message. Only slightly bruised.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?790a9fff0606141624t678e07ddl20d5bdac353aaf1>