Bug 7798 - apachectl stop leaves processes running on OpenBSD 3.0
Summary: apachectl stop leaves processes running on OpenBSD 3.0
Status: CLOSED DUPLICATE of bug 7841
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: All (show other bugs)
Version: 2.0.35
Hardware: Other other
: P3 normal (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-04-06 17:47 UTC by Jim Lippard
Modified: 2004-11-16 19:05 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jim Lippard 2002-04-06 17:47:48 UTC
I currently run Apache 1.3.24 without problems.

I compiled Apache 2.0.35 on OpenBSD 3.0, configured with these options:
# ./configure  --enable-module=ssl --enable-module=auth_db --enable-
module=proxy --enable-module=speling --enable-module=status --e
nable-module=rewrite
#

It compiled and installed without error.

I modified the default configs to point to my existing htdocs and cgi-bins,
but using the default server root, to avoid conflict with the existing
server.  I shut down the existing server and started up Apache 2 with
"apachectl startssl".

This created a bunch of processes running with "-DSSL", but nothing listening
on port 443.  The appropriate SSL logs did not appear in the log dir.  Going to 
the main non-SSL page led to a 403 error, even though permissions are set 
correctly and the server is running as user www group www, same as with 
previous Apache.  The server did not listen on port 443.

Attempting to abort with "apachectl stop" leaves all of the httpd processes 
still running.
Comment 1 Andreas Hasenack 2002-04-07 16:16:17 UTC
apachectl expects to find the PID file in a specific place, /var/run in linux,
for example. I found out that my default httpd.conf was putting it in
/var/log/apache2 instead, that is, the log directory. Changing httpd.conf to
place the pid file in /var/run solved this for me.
Comment 2 Cliff Woolley 2002-04-21 21:28:09 UTC
This discrepancy is fixed in CVS.  Thanks!

*** This bug has been marked as a duplicate of 7841 ***