Date: Wed, 22 Jan 1997 15:29:04 +1100 (EST) From: David Nugent <davidn@unique.usn.blaze.net.au> To: Warner Losh <imp@village.org> Cc: hackers@freebsd.org Subject: Re: Cannot fork Message-ID: <Pine.BSF.3.95.970122152601.3427A-100000@labs.usn.blaze.net.au> In-Reply-To: <E0vmqWF-0000dU-00@rover.village.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 21 Jan 1997, Warner Losh wrote: >How to I get rid of the cannot fork messages? I have maxusers set to >be 30 for my 486 box, yet I still get these messages from time to >time. I just upgraded from Nov 24 -current to Jan 19-current and have >found that the number of times I'm hitting this seems to be much >greater. As others have also said, this is probably due to /etc/login.conf. I committed changes to the default one earlier which should alleviate most of the problems. Otherwise, edit as appropriate. FWIW, the "default" class now modifies mostly soft limits as opposed to hard limits, allowing you to change soft resource limits upwards if it is appropriate. For public systems offering shell accounts, you'd probably need to be a little more strict than that. :-) Regards, David Nugent - Unique Computing Pty Ltd - Melbourne, Australia Voice +61-3-9791-9547 Data/BBS +61-3-9792-3507 3:632/348@fidonet davidn@freebsd.org davidn@blaze.net.au http://www.blaze.net.au/~davidn/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.95.970122152601.3427A-100000>