- Blog
- Howtos
- anything generator
- apache
- asterisk
- autofs
- autoload
- automount
- backup db
- callcentric
- centos
- chumby
- cipher list
- cookies
- ctags
- dns
- dovecot
- glue fleece
- hacking
- httpd
- IE
- iFrame
- ip
- ispconfig
- javascript
- lighttpd
- linux
- media player
- move networks
- mysql
- mysqldiff
- mythtv
- Network Solutions
- openssl
- osx
- os x
- P3P Compact Policy
- php
- postfix
- proftpd
- proxy
- python
- route
- ruby
- screen scraping
- shell
- shell scripts
- slapd
- smb
- ssh
- sshfs
- SSLCertificateChainFile
- sslv2
- stunnel
- suphp
- taglist
- telnet
- trace
- verisign
- vi
- vsftpd
- Scripts
- About
Oops - Downtime
Submitted by adam on Wed, 2008-10-08 21:47.
Oops I managed to not check the results of "/etc/init.d/httpd reload" after setting up another site on the server. To avoid this in the future, I added the following two lines to the end of the reload function in /etc/init.d/httpd:
sleep 1 status $httpd
This will tell you if the httpd process is running:
Reloading httpd: [ OK ] httpd (pid 28299 28298 28297 28296 28295 28294 28293 28292 28265) is running...
Beware though that there is no way to know whether the httpd has processed the -HUP already (aka: reloaded the new config files). For this small load server, 1 second is plenty. For some of my other servers I would probably increase the sleep.
