Better performance that way. Many servers wait for a new connection in a single process, and then fork or create a new thread for the connection. Apache forks before the connection arrives, and one of the processes will get the connection and handle it. You can configure the number of processes in the httpd.conf file.
If you're worried about memory use: you probably shouldn't be. The processes share the majority of their pages, so despite what it looks like 'ps' reports, the total memory use is not much more than just one of the processes. On Tue, 2002-07-23 at 01:56, Ximo Llacer wrote: > > I'd like to know why in my system there are many process about apache. > > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND > root 861 0.0 4.8 79056 6140 ? S Jul22 0:00 /usr/sbin/httpd >-DHAVE_ACCESS -DHAV > apache 880 0.0 4.9 79136 6316 ? S Jul22 0:00 /usr/sbin/httpd >-DHAVE_ACCESS -DHAV ... _______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
