Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.1 6/24/83; site umcp-cs.UUCP Path: utzoo!watmath!clyde!burl!ulysses!allegra!bellcore!decvax!wanginst!ucadmus!harvard!seismo!umcp-cs!chris From: chris@umcp-cs.UUCP (Chris Torek) Newsgroups: net.unix-wizards Subject: Re: maxusers in config file (4BSD) Message-ID: <2515@umcp-cs.UUCP> Date: Tue, 15-Jan-85 23:14:12 EST Article-I.D.: umcp-cs.2515 Posted: Tue Jan 15 23:14:12 1985 Date-Received: Fri, 18-Jan-85 02:03:59 EST References: <1892@burdvax.UUCP> Organization: U of Maryland, Computer Science Dept., College Park, MD Lines: 19 Sigh. ``maxusers'' doesn't limit the number of people who can log in; it's supposed to be the largest number of people you expect to be bashing away at any one time. It controls the size of a lot of system tables. If those tables overflow, you get lots of things printed on your console, and programs won't run, but nothing drastic happens. You can have maxusers set to 10 and have 10 thousand people logged in; the system won't care, but only about 10 of them will have enough resources available to get things done. If you aren't getting ``file table full'' or ``inode table full'' or shell gripes about ``no more processes'' when starting programs, then your maxusers is probably not set too small. -- (This line accidently left nonblank.) In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 7690) UUCP: {seismo,allegra,brl-bmd}!umcp-cs!chris CSNet: chris@umcp-cs ARPA: chris@maryland