home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!europa.eng.gtefsd.com!emory!gatech!swrinde!sdd.hp.com!usc!sol.ctr.columbia.edu!The-Star.honeywell.com!umn.edu!gaia.ucs.orst.edu!flop.ENGR.ORST.EDU!flop.ENGR.ORST.EDU!usenet
- From: toml@skie.ECE.ORST.EDU (Tom Lieuallen)
- Newsgroups: comp.sys.apollo
- Subject: Process limit and locked display
- Date: 28 Jan 1993 18:06:52 GMT
- Organization: College of Engineering, Oregon State University
- Lines: 28
- Distribution: world
- Message-ID: <1k97bsINNfmr@flop.ENGR.ORST.EDU>
- NNTP-Posting-Host: rumba.ece.orst.edu
- Keywords: limits display
-
-
- We are running a mixture of DN 5500 and 425t workstations. Over
- half have 24 MB of RAM, several have 32 MB, and the rest have 16 MB.
- All are running 10.3.5.4 and we have plans to convert to 10.4 soon.
-
- While these machines are prone to problems, several stand out:
-
- 1. Machine runs out of processes. The actual number of running
- processes is not large when it complains of this. It
- is certainly not the 2048 processes that the man pages
- says is the maximum. Do the man pages lie? Is there any
- solution other than rebooting occasionally?
-
- 2. Display locks up. We are running DM and Xapollo. Unfortunately,
- we cannot get rid of either at the moment. Sometimes the
- display stops accepting input from the keyboard and mouse.
- As we cannot restart the DM, our only recourse is to reboot.
- So, does anyone know why the display locks up? Know of
- any solution? Know of a way to restart the DM without
- bringing the machine down to phase 2 (killing the DM with
- any signals thus far brings the machine to phase 2).
-
- These problems are making our Apollos very unreliable. If anyone
- has solutions for us, we would be eternally grateful.
-
- Tom Lieuallen
- Electrical & Computer Engineering Department
- Oregon State University
-