Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!umich!caen.engin.umich.edu!mingin!news
From: paul@speedmetal.engin.umich.edu (Paul Killey)
Newsgroups: comp.unix.ultrix
Subject: Re: Paging problem on Decstaion 3100
Keywords: 3100 paging memory
Message-ID: <1990Apr11.192506.26052@caen.engin.umich.edu>
Date: 11 Apr 90 19:25:00 GMT
References: <10680@cbmvax.commodore.com> <10516@netcom.UUCP> <2112@kiwi.mpr.ca> <22773@netnews.upenn.edu> <2982@decuac.DEC.COM> <23066@netnews.upenn.edu>
Reply-To: paul@speedmetal.engin.umich.edu (Paul Killey)
Organization: University of Michigan College of Engineering
Lines: 20

In article <23066@netnews.upenn.edu> hagan@DCCS.UPENN.EDU (John Dotts Hagan) writes:
>
>Interesting.  I have seen some tasks seem to dump core when started, like:
>% emacs
>Segmentation Fault
>(core dumped)
>%
>but the core file is really from /bin/csh, not emacs!

If you say (emacs) or emacs & or run emacs from /bin/sh you're all
set.  I think because then you get forked, and not vforked.

We get the segmentation fault when trying to run emacs all the time,
but no core file.  Our fix is to have people invoke it one of the ways
indicated above.

We also have the creeping load average till the system hangs at least
once a day on at least one of our machines.

--paul