From owner-freebsd-questions  Mon Apr 28 09:33:21 1997
Return-Path: <owner-questions>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id JAA23032
          for questions-outgoing; Mon, 28 Apr 1997 09:33:21 -0700 (PDT)
Received: from odie.physik2.uni-rostock.de (odie.physik2.uni-rostock.de [139.30.40.28])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA23024
          for <questions@FreeBSD.org>; Mon, 28 Apr 1997 09:33:18 -0700 (PDT)
Received: from odie.physik2.uni-rostock.de (localhost [127.0.0.1])
          by odie.physik2.uni-rostock.de (8.8.3/8.7.3) with ESMTP id SAA21151;
          Mon, 28 Apr 1997 18:33:13 +0200 (MET DST)
Message-Id: <199704281633.SAA21151@odie.physik2.uni-rostock.de>
X-Mailer: exmh version 1.6.7 5/3/96
From: Lars Koeller <Lars_Koeller@odie.physik2.uni-rostock.de>
To: "Paul T. Root" <proot@horton.iaces.com>
cc: questions@FreeBSD.org
Subject: Re: Xperfmon++ on 2.2.1 
In-reply-to: proot's message of Mon, 28 Apr 1997 09:51:32 -0500.
	     <199704281451.JAA17932@horton.iaces.com> 
X-Face: nLQGe[[K51[{{[C\,BiQm[7]u1<r*biUsbPfYvu!Ee"NMw+TUPr`[d`9M2Z@?K79e,e0hGOfWn;9\[H~N.vTWNY>m{N>_\%nLBo4t@)CoZ}hK[W7DwX&V=}Wf#Qb,j:Jpj[(12r=b~:dYmh]fDf\,]_frt6e<dI[U8(?zxR|UKs(CXNU>M<fA||Pim|ljOlWpT$FEK#{iPI$ZdS}V6cx}nyDe"<hSP#6<y33$gO:t{F7o,tYE=4a$ZTF+%7w=UFjMsWObjlS`z9^8$*rOb<rlN{lusO'Ys
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 28 Apr 1997 18:33:12 +0200
Sender: owner-questions@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

----------

Hi!

It's a known problem! Please use the port on my ftp site, or the -current 
ports. They should fix the problem. The 2.2.1 xperfmon package is build on an 
obsolete source base, sorry!

Regards and success

Lars

In reply to "Paul T. Root" who wrote:
 
 > Hi, 
 > 	I upgraded to 2.2.1 from CD over the weekend. It went with
 > out a hitch. Even cooler was that I had the CD in and it booted from
 > that! (Nec SCSI on a 2940) Extra cool!
 > 
 > 	However, afterward I pkg_add xperfmon++ 1.40 and tried running
 > it. Unfortunately, at the first update, it crashes with one of a couple
 > of errors. 'Can't malloc' or 'Can't remalloc'. That's not the real words
 > used, but you get the idea. I tried as me and root, both are in kmem.
 > 
 > 	Any ideas?
 > 
 > Paul.
 > 
 > -- 
 > Sir, I have a cunning plan... - Baldrick

-- 
------------------------------------------------------------------------
Internet:                                       |  Lars Koeller
  Lars_Koeller@odie.physik2.Uni-Rostock.DE      |  Department of Physics
  ftp://odie.physik2.uni-rostock.de             |  University of Rostock
PGP-key:                                        |  Germany
  http://www.nic.surfnet.nl/pgp/pks-toplev.html |

----------- FreeBSD, what else? ---- http://www.freebsd.org ------------