From nobody@FreeBSD.org Wed Nov 7 06:55:15 2001 Return-Path: Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 4E0BA37B405 for ; Wed, 7 Nov 2001 06:55:15 -0800 (PST) Received: (from nobody@localhost) by freefall.freebsd.org (8.11.4/8.11.4) id fA7EtFF08442; Wed, 7 Nov 2001 06:55:15 -0800 (PST) (envelope-from nobody) Message-Id: <200111071455.fA7EtFF08442@freefall.freebsd.org> Date: Wed, 7 Nov 2001 06:55:15 -0800 (PST) From: Michelle Boyce To: freebsd-gnats-submit@FreeBSD.org Subject: kill -HUP {pid} does not reset Apache 2.0 properly X-Send-Pr-Version: www-1.0 >Number: 31823 >Category: ports >Synopsis: kill -HUP {pid} does not reset Apache 2.0 properly >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-ports >State: closed >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed Nov 07 07:00:00 PST 2001 >Closed-Date: Wed Nov 7 07:08:22 PST 2001 >Last-Modified: Wed Nov 07 07:11:24 PST 2001 >Originator: Michelle Boyce >Release: 4.4 Release >Organization: >Environment: 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 >Description: Could be Apache problem but kill -HUP does not reset Apache 2.0 properly. One must kill the daemon completely and re-run it or reboot machine to reset Apache and re-read conf files. Apache 2.0 as loaded off packages, 4.4 release. >How-To-Repeat: kill -hup {apache pid} >Fix: kill -TERM {apache pid} re-run apache >Release-Note: >Audit-Trail: Responsible-Changed-From-To: freebsd-bugs->freebsd-ports Responsible-Changed-By: dd Responsible-Changed-When: Wed Nov 7 07:07:10 PST 2001 Responsible-Changed-Why: ports issue (most likely, anyway; I doubt signals are broken in 4.4) http://www.FreeBSD.org/cgi/query-pr.cgi?pr=31823 State-Changed-From-To: open->closed State-Changed-By: roam State-Changed-When: Wed Nov 7 07:08:22 PST 2001 State-Changed-Why: This is definitely not a FreeBSD problem. You might have better luck asking the port maintainer or reporting the problem to the Apache Group. You might have still better luck using the documented method to send commands to the Apache server, namely using the apachectl utility. http://www.FreeBSD.org/cgi/query-pr.cgi?pr=31823 >Unformatted: