RE: [PHP] apache + mod_php question
| From: | Timothy Hitchens \(HiTCHO\) | Date: | Wed, 08 Jan 2003 19:16:30 +0000 |
| Subject: | RE: [PHP] apache + mod_php question | ||
| References: | 1 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-130789@lists.php.net to get a copy of this message | ||
use: apachectl graceful
It will reload the config's and allow operation to continue!!
See apachectl (help)
start - start httpd
stop - stop httpd
restart - restart httpd if running by sending a SIGHUP or start if
not running
fullstatus - dump a full status screen; requires lynx and mod_status
enabled
status - dump a short status screen; requires lynx and mod_status
enabled
graceful - do a graceful restart by sending a SIGUSR1 or start if not
running
configtest - do a configuration syntax test
help - this screen
Timothy Hitchens (HiTCHO)
Open Platform Consulting
e-mail: tim@hitcho.com.au
> -----Original Message-----
> From: Hugh Beaumont [mailto:hbeaumont@yahoo.com]
> Sent: Thursday, 9 January 2003 5:14 AM
> To: php-general@lists.php.net
> Subject: [PHP] apache + mod_php question
>
>
> Hello,
>
> I have searched the archives and not been able to find the
> solution to
> the following problem. I would be very grateful if someone
> here could help or provide some pointers.
>
> The basic problem is this:
>
> Our apache server will not start if there are system
> processes running that were spawned from apache's last
> invocation (ie. spawned from cgi's, mod_php system() calls,
> etc.). It dies with "cannot bind to ip_address_here port 80", etc.
>
>
> Example:
>
> We restart our servers every so often via crontab in order to
> reload modified conf files, etc. However it appears that if
> a user has spawned a process from mod_php, cgi, etc. that the
> server will not restart until those processes are killed off
> manually.
>
> The worst cases are when badly wrote user scripts allow an
> attacker to upload scripts that bind to a port and attempt to
> make network access, etc. (I would love to disallow users
> from having uploads to the server but
> that is not currently an option).
>
> Does anyone have any suggestion on how to automagically kill
> these processes?
>
> Does anyone have their own favorite recipe for
> stopping/starting apache in an automated fashion.
>
> Right now these situations result in downtime for users and a
> pager in the middle of the night to me! I would very much
> like to stop this :)
>
> Thanks much!
>
>
> __________________________________________________
> Do you Yahoo!?
> Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php