From owner-freebsd-current Thu Sep 30 17:42:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from peak.mountin.net (peak.mountin.net [207.227.119.2]) by hub.freebsd.org (Postfix) with ESMTP id 77CFF14C94 for ; Thu, 30 Sep 1999 17:42:27 -0700 (PDT) (envelope-from jeff-ml@mountin.net) Received: (from daemon@localhost) by peak.mountin.net (8.9.1/8.9.1) id TAA27395; Thu, 30 Sep 1999 19:42:02 -0500 (CDT) (envelope-from jeff-ml@mountin.net) Received: from dial-178.tnt1.rac.cyberlynk.net(209.224.182.178) by peak.mountin.net via smap (V1.3) id sma027393; Thu Sep 30 19:41:45 1999 Message-Id: <3.0.3.32.19990930193723.00936df0@207.227.119.2> X-Sender: jeff-ml@207.227.119.2 X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Thu, 30 Sep 1999 19:37:23 -0500 To: peter.jeremy@alcatel.com.au From: "Jeffrey J. Mountin" Subject: Re: System crash on "vinum start" Cc: freebsd-current@FreeBSD.ORG In-Reply-To: <99Oct1.094141est.40344@border.alcanet.com.au> References: <3.0.3.32.19990930182053.0219b760@207.227.119.2> <19990928084130.L46202@freebie.lemis.com> <19990925104024.B54407@freebie.lemis.com> <199909271705.NAA43302@concours.pc.sas.com> <3.0.3.32.19990927153730.0204c420@207.227.119.2> <19990928084130.L46202@freebie.lemis.com> <99Sep28.125643est.40332@border.alcanet.com.au> <3.0.3.32.19990930182053.0219b760@207.227.119.2> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 09:44 AM 10/1/99 +1000, Peter Jeremy wrote: >I was thinking of some `production' code (written by a sister company) >that I used to provide customer support for. It would regularly core >dump (but was automatically restarted). After a few years they did >manage to fix the core dump, but that exposed a memory leak which they >never did manage to fix (fairly embarrasing in a supposedly >permanently running process). Eeew! Can see your point. Tracking down a sig11 problem in a custom program right now. Seems to be OS related, but think a bit of work around the problem code is in order first. Oh, the pain of learning. My first project fixing another's code. Or at least trying. At least it doesn't harm functionality, so has been bugging me for a while and decided enough is enough. >I gather that root support is the most-asked-for feature in Vinum (when >I asked Greg about it some weeks ago, I got about as far as `when will >Vinum' before he answered me). As long as recovery works, making it >nicer to use is (should be) a lower priority. This was more directed torwards Greg, but would guess that auto-recovery would be fairly requested. Growing plexes (any type) would be #1 on my list, auto-recovery #2, and root #3. Best not to bother him about desired features. Would be nice for a work status/todo list, but then *that* has to be updated. And yet might reduce questions of the "when will" type. Rather like the problem page he added. Otherwise should just stop here now. "Is it done yet? Is it done yet?" 8-0 Jeff Mountin - jeff@mountin.net Systems/Network Administrator FreeBSD - the power to serve '86 Yamaha MaxiumX (not FBSD powered) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message