www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michelle Boyce <miche...@romsoft.net>
Subject general/8701: Kill SIGHUP does not reset 2.0
Date Wed, 07 Nov 2001 15:25:13 GMT

>Number:         8701
>Category:       general
>Synopsis:       Kill SIGHUP does not reset 2.0
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Wed Nov 07 07:30:01 PST 2001
>Originator:     michelle@romsoft.net
>Release:        2.0
FreeBSD 4.4 Release

FreeBSD scorp.romsoft.net 4.4-RELEASE FreeBSD 4.4-RELEASE #0: Tue Sep 18 11:57:08 PDT 2001
    murray@builder.FreeBSD.org:/usr/src/sys/compile/GENERIC  i386

kill -HUP {pid} does not restart Apache 2.0 properly.  Kill -TERM and re-running is the only
method to restart Apache 2.0  Sent report to FreeBSD as well, as I don't know which is the
problem.  NO response required.
kill -HUP {pid} 
kill -TERM {pid}
 [In order for any reply to be added to the PR database, you need]
 [to include <apbugs@Apache.Org> in the Cc line and make sure the]
 [subject line starts with the report component and number, with ]
 [or without any 'Re:' prefixes (such as "general/1098:" or      ]
 ["Re: general/1098:").  If the subject doesn't match this       ]
 [pattern, your message will be misfiled and ignored.  The       ]
 ["apbugs" address is not added to the Cc line of messages from  ]
 [the database automatically because of the potential for mail   ]
 [loops.  If you do not include this Cc, your reply may be ig-   ]
 [nored unless you are responding to an explicit request from a  ]
 [developer.  Reply only with text; DO NOT SEND ATTACHMENTS!     ]

View raw message