On Thursday, 30 September 1999 at 19:37:23 -0500, Jeffrey J. Mountin wrote:
> 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.

You're not typical.  But you *can* grow concatenated plexes.  You just
can't expand UFS to use the space.  That's not a Vinum issue, but
somebody's working on it.

> 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.

That's a good idea, I suppose.  I'll do that.  Done:
http://www.lemis.com/vinum/wishlist.html.

Greg
--
See complete headers for address, home page and phone numbers
finger [EMAIL PROTECTED] for PGP public key


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to