You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by sameer <sa...@c2.net> on 1996/09/03 19:09:08 UTC
Re: nph failure (fwd)
He mentioned "Stronghold" so I don't know if he was talking
about with SSL on or not. But the 1.2<->1.3 difference does look like
it could be a bug introduced between apache 1.0.5 and apache 1.1.1.
>
>
> Someone mentioned nph- bugs the other day but I wasn't paying enough
> attention.
>
> Not acked.
>
> ----- Forwarded message from Homer W. Smith -----
>
> Newsgroups: comp.infosystems.www.servers.unix
> Date: Fri, 30 Aug 1996 23:22:40 -0400 (EDT)
> From: "Homer W. Smith" <ho...@lightlink.com>
> To: apache-bugs@mail.apache.org
> Subject: nph failure (fwd)
> Message-ID: <Pi...@light.lightlink.com>
> MIME-Version: 1.0
> Content-Type: TEXT/PLAIN; charset=US-ASCII
>
>
>
> Running Stronghold 1.3 SunOS 4.1.4
>
> Could someone please tell me why the following nph-tester.cgi returns
> "Document contains no data".
>
> It works fine in Stronghold 1.2.
>
> #!/usr/local/bin/perl
> #
> print "HTTP/1.0 200 OK\n";
> print "Server: $ENV{'SERVER_SOFTWARE'}\n";
> print "MIME-version: 1.0\n";
> print "Content-type: text/plain\n\n";
> print "here is a test\n";
> print "here is a test\n";
> print "here is a test\n";
>
>
> ----- End of forwarded message from Homer W. Smith -----
>
--
Sameer Parekh Voice: 510-986-8770
Community ConneXion, Inc. FAX: 510-986-8777
The Internet Privacy Provider
http://www.c2.net/ sameer@c2.net
What might cause runaway httpd?
Posted by Michael Smith <mj...@cursci.co.uk>.
I got in to work just now to find the following processes have been
eating up CPU time most of the night:
PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND
28285 web 27 0 2220K 900K run 212:40 35.74% 35.74% httpd
25478 web 26 0 2220K 888K run 249:02 33.70% 33.70% httpd
(I am running Solaris 2.5 and apache 1.1.1 with various optional
modules). What might cause this? Is this simply something that happens
with the server every now and then, or is it something caused by bad
CGIing?
Any ideas greatly appreciated; or I guess I'll have to try and set up
some cron job that looks for nasties and kills 'em.
Mike