home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.unix.bsd
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!saimiri.primate.wisc.edu!usenet.coe.montana.edu!gemini.oscs.montana.edu!osynw
- From: osynw@gemini.oscs.montana.edu (Nate Williams)
- Subject: Re: Occasional system hangs
- Message-ID: <1992Dec14.161424.24567@coe.montana.edu>
- Keywords: nn
- Sender: usenet@coe.montana.edu (USENET News System)
- Organization: Montana State University
- References: <1gaclpINN84v@hrd769.brooks.af.mil> <1992Dec11.210430.17335@coe.montana.edu> <a0x9021N2ehg01@JUTS.ccc.amdahl.com>
- Date: Mon, 14 Dec 1992 16:14:24 GMT
- Lines: 30
-
- In article <a0x9021N2ehg01@JUTS.ccc.amdahl.com> gab10@griffincd.amdahl.com (Gary A Browning) writes:
- >In article <1992Dec11.210430.17335@coe.montana.edu>,
- >osynw@gemini.oscs.montana.edu (Nate Williams) writes:
- >> In article <1gaclpINN84v@hrd769.brooks.af.mil>
- >> news@hrd769.brooks.af.mil (InterNet News) writes:
- >> >-Time for more RAM I guess!
- >> >>
- >> >
- >> > I don't think more RAM will help. I have 32M of RAM and and 32M
- >> swap
- >> >partition. It still hangs. nroff is the usual culprit for me.
- >>
- >> The fix for this is to fix G++, re-compile it, and then recompile
- >> groff
- >> with the fixed GCC. The patch for g++ will be in the next patchkit.
- >> [If I ever get it finished :-(]
- >
- >This might be a problem but are you sure it is not simply masking another?
- >A bum compile of a user level program should never cause the system to hang.
- >
- Sorry I didn't make myself clear. Yes, the REAL reason the system is hanging
- is because the kernel has a leak. However, groff has a leak in it which
- magnifies the kernel leak, and fixing groff at least allows the system
- to last longer.
-
- Nate
- --
- osynw@terra.oscs.montana.edu | A hacker w/out a home.
- work: (406) 994-5991 | Keeper of the Unofficial 386BSD Bug Report
- home: (406) 586-0579 | Please send bugs and/or fixes you find.
-