to the running httpd processes. There are two ways to send the signals. First, you can use the unix kill command to directly send signals to the processes. You will notice many httpd executables running will be described in a moment. To send a signal to the parent you should issue a command such as: kill -TERM ‘cat /usr/local/apache2/logs/httpd.pid‘ The second method of signaling the httpd processes apachectl -k stop Sending the TERM or stop signal to the parent causes it to immediately attempt to kill off all of its children. It may take it several seconds to complete killing off its children. Then

to the running httpd processes. There are two ways to send the signals. First, you can use the unix kill command to directly send signals to the processes. You will notice many httpd executables running will be described in a moment. To send a signal to the parent you should issue a command such as: kill -TERM ‘cat /usr/local/apache2/logs/httpd.pid‘ The second method of signaling the httpd processes apachectl -k stop Sending the TERM or stop signal to the parent causes it to immediately attempt to kill off all of its children. It may take it several seconds to complete killing off its children. Then

to the running httpd processes. There are two ways to send the signals. First, you can use the unix kill command to directly send signals to the processes. You will notice many httpd executables running will be described in a moment. To send a signal to the parent you should issue a command such as: kill -TERM `cat /usr/local/apache2/logs/httpd.pid` The second method of signaling the httpd processes apachectl -k stop Sending the TERM or stop signal to the parent causes it to immediately attempt to kill off all of its children. It may take it several seconds to complete killing off its children. Then

to the running httpd processes. There are two ways to send the signals. First, you can use the unix kill command to directly send signals to the processes. You will notice many httpd executables running will be described in a moment. To send a signal to the parent you should issue a command such as: kill -TERM `cat /usr/local/apache2/logs/httpd.pid` The second method of signaling the httpd processes apachectl -k stop Sending the TERM or stop signal to the parent causes it to immediately attempt to kill off all of its children. It may take it several seconds to complete killing off its children. Then

to the running httpd processes. There are two ways to send the signals. First, you can use the unix kill command to directly send signals to the processes. You will notice many httpd executables running will be described in a moment. To send a signal to the parent you should issue a command such as: kill -TERM `cat /usr/local/apache2/logs/httpd.pid` The second method of signaling the httpd processes apachectl -k stop Sending the TERM or stop signal to the parent causes it to immediately attempt to kill off all of its children. It may take it several seconds to complete killing off its children. Then

to the running httpd processes. There are two ways to send the signals. First, you can use the unix kill command to directly send signals to the processes. You will notice many httpd executables running will be described in a moment. To send a signal to the parent you should issue a command such as: kill -TERM `cat /usr/local/apache2/logs/httpd.pid` The second method of signaling the httpd processes apachectl -k stop Sending the TERM or stop signal to the parent causes it to immediately attempt to kill off all of its children. It may take it several seconds to complete killing off its children. Then

to the running httpd processes. There are two ways to send the signals. First, you can use the unix kill command to directly send signals to the processes. You will notice many httpd executables running will be described in a moment. To send a signal to the parent you should issue a command such as: kill -TERM `cat /usr/local/apache2/logs/httpd.pid` The second method of signaling the httpd processes apachectl -k stop Sending the TERM or stop signal to the parent causes it to immediately attempt to kill off all of its children. It may take it several seconds to complete killing off its children. Then

to the running httpd processes. There are two ways to send the signals. First, you can use the unix kill command to directly send signals to the processes. You will notice many httpd executables running will be described in a moment. To send a signal to the parent you should issue a command such as: kill -TERM ‘cat /usr/local/apache2/logs/httpd.pid‘ The second method of signaling the httpd processes apachectl -k stop Sending the TERM or stop signal to the parent causes it to immediately attempt to kill off all of its children. It may take it several seconds to complete killing off its children. Then

to the running httpd processes. There are two ways to send the signals. First, you can use the unix kill command to directly send signals to the processes. You will notice many httpd executables running will be described in a moment. To send a signal to the parent you should issue a command such as: kill -TERM ‘cat /usr/local/apache2/logs/httpd.pid‘ The second method of signaling the httpd processes apachectl -k stop Sending the TERM or stop signal to the parent causes it to immediately attempt to kill off all of its children. It may take it several seconds to complete killing off its children. Then

to the running httpd processes. There are two ways to send the signals. First, you can use the unix kill command to directly send signals to the processes. You will notice many httpd executables running will be described in a moment. To send a signal to the parent you should issue a command such as: kill -TERM ‘cat /usr/local/apache2/logs/httpd.pid‘ The second method of signaling the httpd processes apachectl -k stop Sending the TERM or stop signal to the parent causes it to immediately attempt to kill off all of its children. It may take it several seconds to complete killing off its children. Then