Date: Tue, 2 Sep 1997 00:47:14 -0400 (EDT) From: Brian Clapper <bmc@WillsCreek.COM> To: questions@FreeBSD.ORG Subject: Re: freebsd help Message-ID: <199709020447.AAA01244@current.willscreek.com> In-Reply-To: <123152242@toto.iv>
next in thread | previous in thread | raw e-mail | index | archive | help
Jason <jason@playgal.com> wrote:
[ Playgal.COM? *There's* a new FreeBSD marketing distinction for the web
page, fellas. "FreeBSD even drives some of the many porn sites on the
Internet." ]
> Could anyone with freebsd skills living in fort lauderdale please contact
> me for help.we need to increase the number of processes that apache can
> spawn.
You might try:
1. Bumping up kern.maxprocperuid via sysctl:
sysctl -w kern.maxprocperuid <n>
From sysctl(3):
KERN_MAXPROCPERUID
The maximum number of concurrent processes the system will allow
for a single effective uid. This limit only applies to processes
with an effective uid of nonzero at the time of a fork request.
Processes that have already been started are not affected if the
limit is changed.
2. Bumping up CHILD_MAX in the kernel. From /usr/src/sys/i386/conf/LINT:
#
# Under some circumstances it is convenient to increase the defaults
# for the maximum number of processes per user and the maximum number
# of open files files per user. E.g., (1) in a large news server, user
# `news' may need more than 100 concurrent processes. (2) a user may
# need lots of windows under X. In both cases, it may be inconvenient
# to start all the processes from a parent whose soft rlimit on the
# number of processes is large enough. The following options work by
# changing the soft rlimits for init.
#
options CHILD_MAX=128
See `http://www.apache.org/docs/misc/perf-bsd44.html#detail' for some more
good hints.
-----
Brian Clapper, bmc@WillsCreek.COM, http://WWW.WillsCreek.COM/
If at first you don't succeed, give up, no use being a damn fool.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199709020447.AAA01244>