X-Recipient: archive-cygwin AT delorie DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 42FB43858414 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com; s=default; t=1680533301; bh=ANADVLJSsZQCAGdG9XKvd1IHXTpHoVTJSxBQj460y34=; h=Date:Subject:To:References:In-Reply-To:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To: From; b=iegZA/YZMc2LWbP5I+UzHcgpZzn1vqk4BJj9E8PfP4L67Co3NhhBhInu+1f/T/t9C Dwgh9yKFrpfQvip333DSQ35vvGNX6ftTFWk8MfCQ+2o7B0DuIAZcxmA99dJ3xUvnl/ 0NUrTOVNEDXBTWR0c0ZgZtNykHUqdCmbLO1APpX4= X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org AE0D8385842E Message-ID: <921a8ae6-b272-56b1-abfa-8ce662caaefc@cs.umass.edu> Date: Mon, 3 Apr 2023 10:47:42 -0400 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.9.1 Subject: Re: Cygwin starts take long since march. Three minutes to prompt. Content-Language: en-US To: Thomas Schweikle , "cygwin AT cygwin DOT com" References: <5e891786-ad67-050d-b8c0-aeb250d5303c AT bfs DOT de> In-Reply-To: <5e891786-ad67-050d-b8c0-aeb250d5303c@bfs.de> X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00, JMQ_SPF_NEUTRAL, KAM_DMARC_STATUS, NICE_REPLY_A, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org X-BeenThere: cygwin AT cygwin DOT com X-Mailman-Version: 2.1.29 List-Id: General Cygwin discussions and problem reports List-Archive: List-Post: List-Help: List-Subscribe: , From: Eliot Moss via Cygwin Reply-To: moss AT cs DOT umass DOT edu Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: "Cygwin" On 4/3/2023 10:38 AM, Thomas Schweikle via Cygwin wrote: > Hi! > > Cygwin shell takes about three minutes until the prompt is shown. Any idea how to find out the cause? I think the most common thing in the past had to do with probing remote mounts. You could try pruning paths and see what happens, or adjusting mount parameters. Regards - Eliot Moss -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple