On Wed, Apr 16, 2003 at 11:56:45AM -0600, David Wilk wrote: > However, I've > had apache-ssl die two days in a row, and the culprit appears to be some > process that is sending apache-ssl a SIGUSR1 (what apache-ssl reload or > httpsdctl graceful issues).
Hmmmm... I'm looking at a potato machine now, in /etc/cron.daily/apache-ssl I find: # Send a reload signal to the apache server. if [ -x /usr/bin/killall ] then /usr/bin/killall -HUP apache-ssl else /etc/init.d/apache-ssl reload > /dev/null fi So, if your machine doesn't have an executable killall, you're going to use /etc/init.d/apache-ssl's reload, which: reload) echo -ne "Reloading $NAME configuration.\n" $APACHECTL graceful ;; and $APACHECTL being /usr/sbin/apache-sslctl, the appropriate lines from graceful) are: if $HTTPD -t >/dev/null 2>&1; then if kill -USR1 $PID ; then echo "$0 $ARG: httpd gracefully restarted" else echo "$0 $ARG: httpd could not be restarted" ERROR=7 fi So, there's at least one way to get a USR1 sent to apache-ssl. -- ---- Art Sackett ---- http://www.artsackett.com/ PGP/GPG Public Key: [EMAIL PROTECTED] (autoresponder) In spite of everything, I still believe that people are good at heart. -- Ann Frank