Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Subject: Re: 30 second startup delay on Cygwin programs from SYSTEM account From: Robert Collins To: Scott Atwood Cc: cygwin AT cygwin DOT com In-Reply-To: <200110260107.SAA16481@Xenon.Stanford.EDU> References: <200110260107 DOT SAA16481 AT Xenon DOT Stanford DOT EDU> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/0.15 (Preview Release) Date: 30 Oct 2001 10:59:56 +1100 Message-Id: <1004399998.9189.250.camel@lifelesswks> Mime-Version: 1.0 X-OriginalArrivalTime: 30 Oct 2001 00:04:08.0515 (UTC) FILETIME=[657EA130:01C160D6] On Fri, 2001-10-26 at 11:07, Scott Atwood wrote: > I ran "strace bash" as user SYSTEM and here is an excerpt of the output. > > 2949 226918 [main] bash 1428 internal_getlogin: GetUserName() = SYSTEM > 30450200 30677118 [main] bash 1428 internal_getlogin: Domain: (null), Logon Serv > er: CHARON, Windows Username: SYSTEM > > The output paused for about 30 seconds after the first line printed, and > before the second line printed. Right, here's whats happening: SYSTEM doesn't belong to any network groups - it's local only, but Cygwin is trying to find out it's network data - such as the home domain. Cygwin spawned/forked/execed process's can inherit that data in the cygwin heap IIRC. Which is why no delay is seen - it's been optimised away. But there would be a 30 second delay firing up bash. As for why the 30 second delay in the first place, what's your system config: Are you a member of a win2k AD or an NT4 domain? Are you running NBT? Are you running NTLM? Are you running the Server process? Are you running the workstation process? Cheers, Rob -- 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/