On 12/04/13 18:38, wejii wrote: > I read several times "don't run apache as root". > ps -ef gives me the following: > > root 1448 1 0 Apr11 ? 00:00:04 /usr/sbin/apache2 -k start > www-data 1712 1448 0 Apr11 ? 00:00:00 /usr/sbin/apache2 -k start > www-data 1713 1448 0 Apr11 ? 00:00:00 /usr/sbin/apache2 -k start > www-data 1714 1448 0 Apr11 ? 00:00:00 /usr/sbin/apache2 -k start > www-data 1715 1448 0 Apr11 ? 00:00:00 /usr/sbin/apache2 -k start > www-data 1716 1448 0 Apr11 ? 00:00:00 /usr/sbin/apache2 -k start > www-data 7304 1448 0 11:14 ? 00:00:00 /usr/sbin/apache2 -k start > www-data 7305 1448 0 11:14 ? 00:00:00 /usr/sbin/apache2 -k start > www-data 7306 1448 0 11:14 ? 00:00:00 /usr/sbin/apache2 -k start > > > My question is - what is that root process? Should I ignore it? The root process is required to bind to port 80. It does not serve requests but only monitors its children. The output above shows this in the 3rd column. The root process it the parent of all the other processes. When a child is born one of the first things it does is to change its UID. So, the phrase you cited rather relates to the configuration directive User root But in this case a HTTPD >=2.0 refuses to start if it hasn't been compiled with a special compile time option. So, your processes are completely normal. Nothing to worry about. Torsten --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|