[Prev][Next][Index][Thread]

# Re: declaring prop on #1 crashes server

- Date: Fri, 14 Jun 1996 10:21:51 PDT
- From:
- Content-Type: text/plain; charset="us-ascii"
- In-Reply-to: <9606141501.AA06195@kilpikonna.media.mit.edu>

    Amy wrote:
    >This is reproducable:
    >
    >declaring a new property on #1 crashes our server

    I just tried it on ours, and it is neither reproducable nor reproducible.

    >We are running 1.8.0p5 with some server mods that are attached bellow.

    We are also running 1.8.0p5, and our server mods is just FUP, so I won't
    attach them bellow (nor below).

    >Our machine is a Dec AlphaStation 250 4/266 running OSF/1 V3.2
    >We have 192 Mb of physical RAM and 650 Mb of swap space.
    >The process takes up 134 Mb on booting, and that's what it was
    >taking up when the server crashed.

    Our machine is also a Dec Alpha, running the same system.
    Thanks to FUP, we're far from reaching any RAM limits.
    Any estimate on what the size of your MOO would have been, after adding the
    prop on #1 (how much is max_object() ?), had it not crashed?

    -------------------------------------------------------------
    Gustavo Glusman               Founder/administrator of BioMOO
    -- Gustavo@bioinformatics.weizmann.ac.il
    -- http://bioinformatics.weizmann.ac.il/Gustavo
    -- BioMOO: telnet bioinformatics.weizmann.ac.il 8888
               WWW:   http://bioinfo.weizmann.ac.il/BioMOO

Follow-Ups:

- Re: declaring prop on #1 crashes server

- From: asb@media.mit.edu

References:

- declaring prop on #1 crashes server

- From: Amy Bruckman <asb@media.mit.edu>

- Prev: declaring prop on #1 crashes server
- Next: Re: declaring prop on #1 crashes server
- Index: MOO-cows
- Thread: MOO-cows

Home | Subject Index | Thread Index