home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!ferkel.ucsb.edu!taco!gatech!paladin.american.edu!howland.reston.ans.net!zaphod.mps.ohio-state.edu!ub!galileo.cc.rochester.edu!ee.rochester.edu!jgp
- From: jgp@ee.rochester.edu (Jim Prescott)
- Newsgroups: comp.sys.sun.admin
- Subject: Re: Bringing a Sun to it's knees
- Summary: MAXUPRC can be useful but Sun's default value never is
- Message-ID: <1993Jan26.182030.13896@ee.rochester.edu>
- Date: 26 Jan 93 18:20:30 GMT
- References: <T6AXBYAV@cc.swarthmore.edu> <1993Jan25.221022.28758@ra.msstate.edu>
- Organization: Univ of Rochester, College of Engineering and Applied Science
- Lines: 18
-
- In <1993Jan25.221022.28758@ra.msstate.edu> fwp@CC.MsState.Edu (Frank Peters):
- >If you look in /sys/conf.common/param.c you will see that MAXUPRC (the
- >number of processes per user) is set to 5 less than the total number of
- >processes available. Keeping in mind that the overwhelming number of
- >Suns are single user-at-a-time desktop workstations this makes sense.
-
- Of course since the overwhelming majority of Suns have more than 5 system
- processes the default value of MAXUPRC is pretty useless. Even on a
- single user workstation MAXUPRC should be low enough that the user doesn't
- interfere with normal system operation.
-
- A related limitation that probably applies to Suns is that only root can
- allocate the last process slot. This is to allow root a chance of cleaning
- up after runaway processes without rebooting. In many cases such a cleanup
- would be much easier if root had a few more dedicated slots (like maybe 5 :-).
- --
- Jim Prescott - Systems Staff jgp@ee.rochester.edu rutgers!ur-valhalla!jgp
- College of Engineering and Applied Science, University of Rochester, NY
-