Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Reply-To: <wpmccormick AT covad DOT net>
From: "Bill McCormick" <wpmccormick AT covad DOT net>
To: "Cygwin" <cygwin AT cygwin DOT com>
Subject: apache runaway
Date: Mon, 22 Sep 2003 21:24:17 -0500
Message-ID: <NDBBLLFMLFMANIDPNADCIENPFGAA.wpmccormick@covad.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
Note-from-DJ: This may be spam

I believe I have found a case where Apache (or some httpd children) steal
all processor time:

Here are what appear to be the conditions:

1. Have directories (such as for log files) owned by SYSTEM.None
2. Start Apache from Windows Services as LocalSystem
3. as some user other than SYSTEM ... $apachectrl restart

I think that should reproduce the problem. Be aware that it may take some
time to get your system back again by killing the runaway httpd processes
through the Windoz task manager.

Now I've several dir's for log files (VHosts) so I haven't bothered to
actually verify that chown'ing these dir's to something else makes this
problem disappear. But I think this is a pretty good WAG as to how to
reproduce this problem. If not, let me know and I can try to provide more
info as necessary.

Bill
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.518 / Virus Database: 316 - Release Date: 9/11/2003


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/