delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2001/10/26/09:53:08

Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Message-Id: <4.3.1.2.20011026093939.01821548@pop.ma.ultranet.com>
X-Sender: lhall AT pop DOT ma DOT ultranet DOT com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Date: Fri, 26 Oct 2001 09:46:50 -0400
To: Scott Atwood <atwood AT CS DOT Stanford DOT EDU>, cygwin AT cygwin DOT com
From: "Larry Hall (RFK Partners, Inc)" <lhall AT rfk DOT com>
Subject: Re: 30 second startup delay on Cygwin programs from SYSTEM
account
In-Reply-To: <200110252315.QAA01067@Xenon.Stanford.EDU>
Mime-Version: 1.0

FAQ entry

Why is Cygwin suddenly so slow?
http://www.cygwin.com/faq/faq_4.html#SEC32

is a good hint.  Focus on the fact that network shares (or drives) in the
path are an issue, not necessarily the recent change that makes the now
obsolete //X drive syntax equivalent to a network path.  While this may be 
your problem, references to network directories in your path is a timeless
issue that can account for the behavior you describe.  There are multiple
posts about this in the mail archives, although they are likely to be 
buried fairly far back in the archives and may be difficult to unearth 
if you don't happen to hit a keyword used in those messages. ;-)

Larry Hall                              lhall AT rfk DOT com
RFK Partners, Inc.                      http://www.rfk.com
118 Washington Street                   (508) 893-9779 - RFK Office
Holliston, MA 01746                     (508) 893-9889 - FAX


At 07:15 PM 10/25/2001, Scott Atwood wrote:
>I am running Cygwin 1.3.3 on Windows 2000 Server, and I have noticed a
>strange problem.  Whenever I try to start a Cygwin process from a windows
>cmd shell as the user SYSTEM, there is an approximately 30 second delay
>before the process starts.  If I have started a bash process as SYSTEM,
>subesequent processes started from within bash start normally.  Cygwin
>processes always start normally for the Administrator user.
>
>I have looked in the FAQ and the documentation, searched Google, and
>searched the Cygwin mailing list archive, and I couldn't find any
>mention of this problem.
>
>-Scott
>
>-- 
>Scott Atwood
>atwood AT cs DOT stanford DOT edu
>PGP key fingerprint:  2852 FAE0 B0BB FE52 7002  1019 4D48 78B3 6FF0 A89F
>
>--
>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/


--
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/

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019