DO NOT REPLY [Bug 10781] - Can not see the pdf files on my server on the forms page.

2002-07-18 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10781.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10781

Can not see the pdf files on my server on the forms page.

[EMAIL PROTECTED] changed:

   What|Removed |Added

   Platform|Alpha   |All



--- Additional Comments From [EMAIL PROTECTED]  2002-07-18 00:43 ---
I have found that 1.3.26 works with PDFs.  The platform somehow got changed to 
alpha and it should be all.  I think that the severity may have to be changed 
to Critical.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



DO NOT REPLY [Bug 10932] New: - Improper negative LocationMatch behavior

2002-07-18 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10932.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10932

Improper negative LocationMatch behavior

   Summary: Improper negative LocationMatch behavior
   Product: Apache httpd-2.0
   Version: 2.0.39
  Platform: PC
OS/Version: Linux
Status: NEW
  Severity: Normal
  Priority: Other
 Component: Core
AssignedTo: bugs@httpd.apache.org
ReportedBy: [EMAIL PROTECTED]


I've googled, and fiddled to no ends. I have what I believe to
be a simple goal. I wish to:

LocationMatch !^/bar
ProxyPass http://somehost
/LocationMatch

Location /bar
handler
/Location

The specific regexp used doesn't matter. the instant I add !
which is supposed
to be the negation character /bar is passed to the handler
properly, but
anything else is not proxied but served from the local system
instead.

So to reiterate what is desired:
everything but /bar goes to somehost
/bar is handled locally

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



DO NOT REPLY [Bug 10774] - apr_shm_create core dump

2002-07-18 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10774.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10774

apr_shm_create core dump





--- Additional Comments From [EMAIL PROTECTED]  2002-07-18 03:07 ---
All I get is:
#0  0x40079361 in apr_shm_create (m=0x3d363074, reqsize=0, 
filename=0x4482 Address 0x4482 out of bounds, pool=0x4482) at shm.c:410

from where and/or bt
even with --enable-maintainer-mode

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



DO NOT REPLY [Bug 10774] - apr_shm_create core dump

2002-07-18 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10774.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10774

apr_shm_create core dump





--- Additional Comments From [EMAIL PROTECTED]  2002-07-18 03:31 ---
can you attach the apr.h, apr_private.h, config.nice, and your httpd 
configuration.

this will help us determine your machine configuration.

also in
srclib/apr/test there is a program called 'testshm.c' can you run this test and
see if it also fails

Thanks
Ian

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



DO NOT REPLY [Bug 10774] - apr_shm_create core dump

2002-07-18 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10774.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10774

apr_shm_create core dump





--- Additional Comments From [EMAIL PROTECTED]  2002-07-18 03:44 ---
Created an attachment (id=2389)
tar.gz of apr.h, apr_private.h, config.nice, and httpd configuration

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



DO NOT REPLY [Bug 10774] - apr_shm_create core dump

2002-07-18 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10774.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10774

apr_shm_create core dump





--- Additional Comments From [EMAIL PROTECTED]  2002-07-18 03:47 ---
testshm dumps core as well, however the trace doesn't yield much:
Program terminated with signal 11, Segmentation fault.
Cannot access memory at address 0x40016e20.
#0  0x0 in ?? ()

I should probably note that this problem exists in some later versions of apache
1.x as well. (I'm currently running Apache/1.3.12 fine).

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



DO NOT REPLY [Bug 7513] - Proxy not downgrading responses for HTTP/1.0 clients

2002-07-18 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7513.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7513

Proxy not downgrading responses for HTTP/1.0 clients





--- Additional Comments From [EMAIL PROTECTED]  2002-07-18 04:36 ---
Oops.  I meant a security-patched version of 1.3.20 (not 1.3.26)

Actually, on futher investigation, I beleive there is something else going on. 
I am not seeing evidence of a chunked encoding problem when running a proxy
through a 1.3.26 server with most pages.  However, there is one page, and error
handling page, that uses CGI::Carp to override the die() method and pops up our
own custom error message in a new window (via Javascript) and logs the error
into a database.  This page no longer works with the 1.3.26 HTTP/1.1 proxy code,
and returns garbled  HTML (shown in the attached document 1.3.26_response.txt,
as compared with the correctly functioning page returned 1.2.30_reponse.txt)

I am going to do some more experiementing to see if I can isolate the problem
some more.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



DO NOT REPLY [Bug 7513] - Proxy not downgrading responses for HTTP/1.0 clients

2002-07-18 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7513.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7513

Proxy not downgrading responses for HTTP/1.0 clients





--- Additional Comments From [EMAIL PROTECTED]  2002-07-18 04:37 ---
Created an attachment (id=2391)
corrupted HTML sent by 1.3.26 mod_proxy

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



DO NOT REPLY [Bug 7513] - Proxy not downgrading responses for HTTP/1.0 clients

2002-07-18 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7513.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7513

Proxy not downgrading responses for HTTP/1.0 clients





--- Additional Comments From [EMAIL PROTECTED]  2002-07-18 04:38 ---
Created an attachment (id=2392)
working HTML from 1.3.20 mod_proxy

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



DO NOT REPLY [Bug 10939] New: - directory listing errors

2002-07-18 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10939.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10939

directory listing errors

   Summary: directory listing errors
   Product: Apache httpd-1.3
   Version: 1.3.26
  Platform: Sun
OS/Version: Solaris
Status: NEW
  Severity: Major
  Priority: Other
 Component: Other
AssignedTo: bugs@httpd.apache.org
ReportedBy: [EMAIL PROTECTED]
CC: [EMAIL PROTECTED]


We try to use apache_1.3.26. The content listing of the directory is not
viewable anymore. It worked fine with earlier versions of apache i.e.
apache_1.3.6. If I choose a special file in this directory tree for viewing , it
works fine. there're no access restrictions for the whole filesystem. the size
of the files/subdirectories varies between some kB and 10 MB.

seeerrorlogs and failure display below

error_log:
[Wed Jul 17 16:22:53 2002] [notice] child pid 7247 exit signal Bus Error (10)

message 
through proxy access:
zero sized reply

access without proxy:
the document contains no data (netscape)
page cannot be displayed (internet explorer)

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



DO NOT REPLY [Bug 10942] New: - Segmentation fault using GD - GD::Text::Align

2002-07-18 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10942.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10942

Segmentation fault using GD - GD::Text::Align

   Summary: Segmentation fault using GD - GD::Text::Align
   Product: Apache httpd-1.3
   Version: 1.3.26
  Platform: PC
   URL: http://www.topconcepts.de
OS/Version: Linux
Status: NEW
  Severity: Normal
  Priority: Other
 Component: Other mods
AssignedTo: bugs@httpd.apache.org
ReportedBy: [EMAIL PROTECTED]
CC: [EMAIL PROTECTED]


Issuing the following command in perl:

my $image=new GD::Image($width,$height);

if either $width or $height is zero, apache writes the following to
the error_log

gd-png:  fatal libpng error: Image width or height is zero in IHDR
gd-png error: setjmp returns error condition

Which is not too strange --- 
but taking a look at /var/log/httpd.error_log shows additionally:

[notice] child pid 6764 exit signal Segmentation fault (11)

Even if the intitial error may be somewhere in the GD.pm - I don't
think, that Apache should crash its childs, should it?

Maybe you can have a look into it,

thanks

Henrik Steffen
www.topconcepts.de

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



DO NOT REPLY [Bug 10946] New: - redundant slashes in urls cause 403 Forbidden errors

2002-07-18 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10946.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10946

redundant slashes in urls cause 403 Forbidden errors

   Summary: redundant slashes in urls cause 403 Forbidden errors
   Product: Apache httpd-2.0
   Version: 2.0.39
  Platform: PC
OS/Version: Linux
Status: NEW
  Severity: Normal
  Priority: Other
 Component: Core
AssignedTo: bugs@httpd.apache.org
ReportedBy: [EMAIL PROTECTED]
CC: [EMAIL PROTECTED]


Trying to retrieve http://foo.ximian.com/bar.html will work, but trying to
retrieve http://foo.ximian.com//bar.html (note the redundant slashes) fails with
a 403.  For what it's worth, http://foo.ximian.com/baz//baz.html works OK.  

As a workaround, I used mod_rewrite in a manner similar to this:
RewriteEngine On
RewriteRule ^//(.*$) /path/to/docroot/$1
This works, and the performance hit doesn't seem to be especially great, but it
isn't ideal.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



DO NOT REPLY [Bug 10939] - directory listing errors

2002-07-18 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10939.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10939

directory listing errors

[EMAIL PROTECTED] changed:

   What|Removed |Added

  Component|Other   |mod_autoindex



--- Additional Comments From [EMAIL PROTECTED]  2002-07-18 15:02 ---
Is this the same for all directories or just for particular directories?
What are the characteristics of the directories where it happens (ie.
very large number of files, special filenames, etc).

Can you figure out how to get a core file and provide a backtrace?

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



DO NOT REPLY [Bug 10932] - Allow Negative regex in LocationMatch

2002-07-18 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10932.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10932

Allow Negative regex in LocationMatch

[EMAIL PROTECTED] changed:

   What|Removed |Added

   Severity|Normal  |Enhancement
   Priority|Other   |Low
Summary|Improper negative   |Allow Negative regex in
   |LocationMatch behavior  |LocationMatch



--- Additional Comments From [EMAIL PROTECTED]  2002-07-18 15:11 ---
I don't believe that the LocationMatch/DirectoryMatch/FilesMatch sections
allow negatives.  The ! syntax is certainly not documented anywhere.

I guess we could consider this bug report a request for such ability.  I have
seen it requested elsewhere, and it shouldn't be that difficult to provide.

As far as your particular problem, it should be easy to get around using 
something
like
RewriteEngine On
RewriteCond %{REQUEST_URI} !^/bar
RewriteRule / http://somehost/ [P]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



DO NOT REPLY [Bug 7513] - Proxy not downgrading responses for HTTP/1.0 clients

2002-07-18 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7513.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7513

Proxy not downgrading responses for HTTP/1.0 clients

[EMAIL PROTECTED] changed:

   What|Removed |Added

   Severity|Blocker |Normal



--- Additional Comments From [EMAIL PROTECTED]  2002-07-18 15:26 ---
I've been digging much deeper into this, and alas it appears to be a 
problem with the way the developers programmed the error handling code:  
They are using it to print HTML and JavaScript that ends up getting printed 
BEFORE the actual HTTP 500 headers, and this this is corrupting the 
headers in a way that just happens to work OK when proxied with HTTP/1.0 
(under 1.3.20) but not with the HTTP/1.1 proxy code (which seems to be 
stripping out some of the HTML boilerplate tags that cause the JavaScript 
functionality to fail on the browser-side.  (At least I think that is what 
is happpening) I need to discuss this with our developers to determine if 
there is a better (correct) way to handle errors, or look into overriding 
Apache's error handling of 500 server errors.

For those that are interested (maybe nobody :) I have attached two more 
ASCII dumps of the HTTP/HTML returned to the client browser by both the 
1.3.20 proxy and 1.3.26 proxy.  

I think this bug can be closed, but I'll leave it up to actual Apache 
developers to determine if this really isn't a problem (which it now seems 
to me that it isn't.)

Sorry for the confusion...

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



DO NOT REPLY [Bug 7513] - Proxy not downgrading responses for HTTP/1.0 clients

2002-07-18 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7513.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7513

Proxy not downgrading responses for HTTP/1.0 clients





--- Additional Comments From [EMAIL PROTECTED]  2002-07-18 15:30 ---
Created an attachment (id=2397)
HTTP/HTML output from 1.3.20 proxy

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



DO NOT REPLY [Bug 7513] - Proxy not downgrading responses for HTTP/1.0 clients

2002-07-18 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7513.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7513

Proxy not downgrading responses for HTTP/1.0 clients





--- Additional Comments From [EMAIL PROTECTED]  2002-07-18 15:31 ---
Created an attachment (id=2398)
HTTP/HTML output from 1.3.26 proxy

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



DO NOT REPLY [Bug 10961] New: - Redirect inside of Directory XYZ does not pass environment back to the browser

2002-07-18 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10961.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10961

Redirect inside of Directory XYZ does not pass environment back to the browser

   Summary: Redirect inside of Directory XYZ does not pass
environment back to the browser
   Product: Apache httpd-1.3
   Version: 1.3.26
  Platform: Sun
OS/Version: Linux
Status: NEW
  Severity: Normal
  Priority: Other
 Component: core
AssignedTo: bugs@httpd.apache.org
ReportedBy: [EMAIL PROTECTED]


The following configuration example causes loss of the query string...

Servername xxx.xxx.com
#ScriptAlias /cgi-bin/ /usr/local/apache/cgi-bin
Directory /
Redirect /cgi-bin/ http://yyy.xxx.com/cgi-bin/

...

/Directory

-
With the above config -
Browser is pointed to http://xxx.xxx.com/cgi-bin/some.cgi?q=abc
Browser is sent a 302 with new location at http://yyy.xxx.com/cgi-bin/some.cgi
-

Using the redirect outside of the Directory XYZ block functions properly

ServerName xxx.xxx.com
#ScriptAlias /cgi-bin/ /usr/local/apache/cgi-bin/
Redirect /cgi-bin/ http://yyy.xxx.com/cgi-bin/
Directory /
...
/Directory


Browser points to http://xxx.xxx.com/cgi-bin/some.cgi?q=abc
Browser is sent a 302 with location of http://yyy.xxx.com/cgi-bin/some.cgi?q=abc


I have tested this repeatedly on RedHat 7.3 and Solaris 8.  Verifying both
visually with the browser and a network sniff.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



DO NOT REPLY [Bug 10937] - apachectl stop doesn't stop httpd processes

2002-07-18 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10937.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10937

apachectl stop doesn't stop httpd processes





--- Additional Comments From [EMAIL PROTECTED]  2002-07-18 22:22 ---
Have you tried sending a kill signal directly to the process listed
in the pid file?

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]