Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Message-ID: <00f501c2bd8f$2b546780$78d96f83@POMELLO>
From: "Max Bowsher" <maxb@ukf.net>
To: "Elfyn McBratney" <elfyn-cygwin@exposure.org.uk>, <cygwin@cygwin.com>
References: <Pine.GSO.4.44.0301161236100.10883-100000@slinky.cs.nyu.edu> <011501c2bd8e$02f8a310$0d6186d9@webdev>
Subject: Re: cygrunsrv and apache
Date: Thu, 16 Jan 2003 18:43:32 -0000
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106

Elfyn McBratney wrote:
> Igor,
>
>> Just for kicks, did you try starting Apache from a SYSTEM-owned
>> shell?
>> I posted instructions on how to get one to this list a couple of
>> months ago.  It'd be interesting to know whether it works.
>> Certainly would eliminate some variables from the equation (i.e.,
>> the username).
>
> I cant seem to get htdig to help me find it... It's awfully slow. I'm
> going through the archives by hand starting in October '02 so I hope
> to find it ;-)

To do it with no extra tools, you can do run "at hh:mm /interactive cmd",
with hh:mm being the next minute. Then you just have to wait for the Task
Scheduler to give you your shell when the clock ticks over.

Alternatively, http://www.google.co.uk/search?q=cmdasuser is a convenient
little program, to accomplish this without the wait.

Once you have your cmd shell, just run bash, and go from there.

Max.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

