This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
Re: 30 second startup delay on Cygwin programs from SYSTEM account
- To: Scott Atwood <atwood at CS dot Stanford dot EDU>
- Subject: Re: 30 second startup delay on Cygwin programs from SYSTEM account
- From: Robert Collins <robert dot collins at itdomain dot com dot au>
- Date: 30 Oct 2001 10:59:56 +1100
- Cc: cygwin at cygwin dot com
- References: <200110260107.SAA16481@Xenon.Stanford.EDU>
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/